Method for exception case of minimum applicable k0 in wireless communication system, and terminal using method

ABSTRACT

The present specification provides a method for receiving downlink control information performed by a terminal in a wireless communication system, wherein the method is characterized in that the downlink control information is received from a base station and includes minimum applicable scheduling offset information, and the minimum applicable scheduling offset information informs a minimum applicable slot offset and receives a physical downlink shared channel (PDSCH) from the base station on a slot having a slot offset value equal to or greater than a value of the minimum applicable slot offset.

BACKGROUND OF THE DISCLOSURE

This application is a Continuation Application of U.S. application Ser.No. 17/383,344, filed on Jul. 22, 2021, which is a Continuation BypassApplication of International Application No. PCT/KR2020/004297, filed onMar. 30, 2020, which claims the benefit of and priority to KoreanApplication No. 10-2019-0037022, filed on Mar. 29, 2019, KoreanApplication No. 10-2019-0038418, filed on Apr. 2, 2019, KoreanApplication No. 10-2019-0052494, filed on May 3, 2019 and U.S.Provisional Application No. 62/847,296, filed on May 13, 2019, thecontents of which are all hereby incorporated by reference herein intheir entirety.

FIELD OF THE DISCLOSURE

The present specification relates to wireless communication.

RELATED ART

As a wider range of communication devices require larger communicationcapacities, the need for mobile broadband communication that is moreenhanced than the existing Radio Access Technology (RAT) is rising.Additionally, massive Machine Type Communications (massive MCT), whichconnects multiple devices and objects so as to provide various servicesregardless of time and place, is also one of the most important issuesthat are to be considered in the next generation communication.Moreover, discussions are made on services/terminals (or user equipment(UE)) that are sensitive to reliability and latency. And, discussionsare made on the adoption of a next generation radio access technologythat is based on the enhanced mobile broadband communication, massiveMTC, Ultra-Reliable and Low Latency Communication (URLLC), and so on.And, for convenience, the corresponding technology will be referred toas a new radio access technology (new RAT or NR).

Hereinafter, in the present specification, a method of efficientlyreducing power consumption of a UE using cross-slot scheduling isproposed.

SUMMARY OF THE DISCLOSURE Technical Solutions

In an aspect, a method for receiving downlink control information in awireless communication system is provided. The method may be performedby a user equipment (UE) and comprise receiving, from a base station,the downlink control information, wherein the downlink controlinformation includes minimum applicable scheduling offset information,wherein the minimum applicable scheduling offset information informs aminimum applicable slot offset and receiving, from the base station, aphysical downlink shared channel (PDSCH) on a slot having a value of aslot offset equal to or greater than a value of the minimum applicableslot offset.

Effects of the Disclosure

According to the present specification, there is an effect ofefficiently reducing power consumption of the UE by using cross-slotscheduling.

The effects that can be obtained through a specific example of thepresent specification are not limited to the effects listed above. Forexample, there may be various technical effects that a person havingordinary skill in the related art can understand or derive from thepresent specification. Accordingly, specific effects of the presentspecification are not limited to those explicitly described in thepresent specification, and may include various effects that can beunderstood or derived from the technical features of the presentspecification.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication system.

FIG. 2 is a diagram showing a wireless protocol architecture for a userplane.

FIG. 3 is a diagram showing a wireless protocol architecture for acontrol plane.

FIG. 4 illustrates a system structure of a new generation radio accessnetwork (NG-RAN) to which NR is applied.

FIG. 5 illustrates functional partitioning between NG-RAN and SGC.

FIG. 6 illustrates a frame structure applicable in NR.

FIG. 7 illustrates a CORESET.

FIG. 8 is a view illustrating a difference between a legacy controlregion and a CORESET in the NR.

FIG. 9 illustrates an example of a frame structure for the new radioaccess technology (new RAT).

FIG. 10 is an abstract diagram of a hybrid beamforming structure in theviewpoints of the TXRU and physical antenna.

FIG. 11 is a schematic diagram of the beam sweeping operation for asynchronization signal and system information during a downlink (DL)transmission process.

FIG. 12 shows examples of 5G usage scenarios to which the technicalfeatures of the present specification can be applied.

FIG. 13 illustrates a scenario in which three different bandwidth partsare configured.

FIG. 14 schematically shows an example of cross-slot scheduling.

FIG. 15 is a flowchart of a method for receiving a PDSCH based on adefault PDSCH time domain resource allocation according to an embodimentof the present specification.

FIG. 16 is a flowchart of a method for receiving a PDSCH based on adefault PDSCH time domain resource allocation according to anotherembodiment of the present specification.

FIG. 17 is a flowchart of a method for receiving a PDSCH based on adefault PDSCH time domain resource allocation from a terminalperspective according to an embodiment of the present specification.

FIG. 18 is a block diagram of an apparatus for receiving a PDSCH basedon a default PDSCH time domain resource allocation from a terminalperspective according to an embodiment of the present specification.

FIG. 19 is a flowchart of a method for transmitting a PDSCH based ondefault PDSCH time domain resource allocation from a base stationperspective according to an embodiment of the present specification.

FIG. 20 is a block diagram of a PDSCH transmission apparatus based ondefault PDSCH time domain resource allocation from a base stationperspective according to an embodiment of the present specification.

FIG. 21 shows an exemplary communication system (1), according to anembodiment of the present specification.

FIG. 22 shows an exemplary wireless device to which the presentspecification can be applied.

FIG. 23 shows another example of a wireless device applicable to thepresent specification.

FIG. 24 shows a signal process circuit for a transmission signalaccording to an embodiment of the present specification.

FIG. 25 shows another example of a wireless device according to anembodiment of the present specification.

FIG. 26 shows a hand-held device to which the present specification isapplied.

FIG. 27 shows a vehicle or an autonomous vehicle to which the presentspecification is applied.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

In the present specification, “A or B” may mean “only A”, “only B” or“both A and B”. In other words, in the present specification, “A or B”may be interpreted as “A and/or B”. For example, in this specification,“A, B or C” refers to “only A”, “only B”, “only C”, or “any combinationof A, B and C”.

A forward slash (/) or comma used herein may mean “and/or”. For example,“A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “onlyB”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”.

In the present specification, “at least one of A and B” may mean “onlyA”, “only B”, or “both A and B”. In addition, in the presentspecification, the expression “at least one of A or B” or “at least oneof A and/or B” can be interpreted the same as “at least one of A and B”.

In addition, in the present specification, “at least one of A, B and C”means “only A”, “only B”, “only C”, or “any combination of A, B and C”.In addition, “at least one of A, B or C” or “at least one of A, B and/orC” can mean “at least one of A, B and C”.

In addition, parentheses used in the present specification may mean “forexample”. Specifically, when described as “control information (PDCCH)”,“PDCCH” may be proposed as an example of “control information”. In otherwords, “control information” of the present specification is not limitedto “PDCCH”, and “PDDCH” may be suggested as an example of “controlinformation”. In addition, even when described as “control information(i.e., PDCCH)”, “PDCCH” may be proposed as an example of “controlinformation”.

In the present specification, technical features that are individuallydescribed in one drawing may be implemented individually or at the sametime.

FIG. 1 illustrates a wireless communication system. The wirelesscommunication system may also be referred to as an evolved-UMTSterrestrial radio access network (E-UTRAN), or long term evolution(LTE)/LTE-A system.

The E-UTRAN includes at least one base station (BS) (20) which providesa control plane and a user plane to a user equipment (UE) (10). The UE(10) may be fixed or mobile, and may be referred to as anotherterminology, such as a mobile station (MS), a user terminal (UT), asubscriber station (SS), a mobile terminal (MT), a wireless device, andso on. The BS (20) is generally a fixed station that communicates withthe UE (10) and may be referred to as another terminology, such as anevolved node-B (eNB), a base transceiver system (BTS), an access point,and so on.

The BSs (20) are interconnected by means of an X2 interface. The BSs(20) are also connected by means of an S1 interface to an evolved packetcore (EPC) (30), more specifically, to a mobility management entity(MME) through S1-MME and to a serving gateway (S-GW) through

The EPC (30) includes an MME, an S-GW, and a packet data network-gateway(P-GW). The MME has access information of the UE or capabilityinformation of the UE, and such information is generally used formobility management of the UE. The S-GW is a gateway having an E-UTRANas an end point. The P-GW is a gateway having a PDN as an end point.

Layers of a radio interface protocol between the UE and the network canbe classified into a first layer (L1), a second layer (L2), and a thirdlayer (L3) based on the lower three layers of the open systeminterconnection (OSI) model that is well-known in the communicationsystem. Among them, a physical (PHY) layer belonging to the first layerprovides an information transfer service by using a physical channel,and a radio resource control (RRC) layer belonging to the third layerserves to control a radio resource between the UE and the network. Forthis, the RRC layer exchanges an RRC message between the UE and the BS.

FIG. 2 is a diagram showing a wireless protocol architecture for a userplane. FIG. 3 is a diagram showing a wireless protocol architecture fora control plane. The user plane is a protocol stack for user datatransmission. The control plane is a protocol stack for control signaltransmission.

Referring to FIGS. 2 and 3 , a PHY layer provides an upper layer with aninformation transfer service through a physical channel. The PHY layeris connected to a medium access control (MAC) layer which is an upperlayer of the PHY layer through a transport channel Data is transferredbetween the MAC layer and the PHY layer through the transport channel.The transport channel is classified according to how and with whatcharacteristics data is transferred through a radio interface.

Data is moved between different PHY layers, that is, the PHY layers of atransmitter and a receiver, through a physical channel. The physicalchannel may be modulated according to an Orthogonal Frequency DivisionMultiplexing (OFDM) scheme, and use the time and frequency as radioresources.

The functions of the MAC layer include mapping between a logical channeland a transport channel and multiplexing and demultiplexing to atransport block that is provided through a physical channel on thetransport channel of a MAC Service Data Unit (SDU) that belongs to alogical channel. The MAC layer provides service to a Radio Link Control(RLC) layer through the logical channel

The functions of the RLC layer include the concatenation, segmentation,and reassembly of an RLC SDU. In order to guarantee various types ofQuality of Service (QoS) required by a Radio Bearer (RB), the RLC layerprovides three types of operation mode: Transparent Mode (TM),Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provideserror correction through an Automatic Repeat Request (ARQ).

The RRC layer is defined only on the control plane. The RRC layer isrelated to the configuration, reconfiguration, and release of radiobearers, and is responsible for control of logical channels, transportchannels, and PHY channels. An RB means a logical route that is providedby the first layer (PHY layer) and the second layers (MAC layer, the RLClayer, and the PDCP layer) in order to transfer data between UE and anetwork.

The function of a Packet Data Convergence Protocol (PDCP) layer on theuser plane includes the transfer of user data and header compression andciphering. The function of the PDCP layer on the user plane furtherincludes the transfer and encryption/integrity protection of controlplane data.

What an RB is configured means a procedure of defining thecharacteristics of a wireless protocol layer and channels in order toprovide specific service and configuring each detailed parameter andoperating method. An RB can be divided into two types of a Signaling RB(SRB) and a Data RB (DRB). The SRB is used as a passage through which anRRC message is transmitted on the control plane, and the DRB is used asa passage through which user data is transmitted on the user plane.

If RRC connection is established between the RRC layer of UE and the RRClayer of an E-UTRAN, the UE is in the RRC connected state. If not, theUE is in the RRC idle state.

A downlink transport channel through which data is transmitted from anetwork to UE includes a broadcast channel (BCH) through which systeminformation is transmitted and a downlink shared channel (SCH) throughwhich user traffic or control messages are transmitted. Traffic or acontrol message for downlink multicast or broadcast service may betransmitted through the downlink SCH, or may be transmitted through anadditional downlink multicast channel (MCH). Meanwhile, an uplinktransport channel through which data is transmitted from UE to a networkincludes a random access channel (RACH) through which an initial controlmessage is transmitted and an uplink shared channel (SCH) through whichuser traffic or control messages are transmitted.

Logical channels that are placed over the transport channel and that aremapped to the transport channel include a broadcast control channel(BCCH), a paging control channel (PCCH), a common control channel(CCCH), a multicast control channel (MCCH), and a multicast trafficchannel (MTCH).

The physical channel includes several OFDM symbols in the time domainand several subcarriers in the frequency domain. One subframe includes aplurality of OFDM symbols in the time domain. An RB is a resourcesallocation unit, and includes a plurality of OFDM symbols and aplurality of subcarriers. Furthermore, each subframe may use specificsubcarriers of specific OFDM symbols (e.g., the first OFDM symbol) ofthe corresponding subframe for a physical downlink control channel(PDCCH), that is, an L1/L2 control channel A Transmission Time Interval(TTI) is a unit time for subframe transmission.

Hereinafter, a new radio access technology (new RAT, NR) will bedescribed.

As a wider range of communication devices require larger communicationcapacities, the need for mobile broadband communication that is moreenhanced than the existing Radio Access Technology (RAT) is rising.Additionally, massive Machine Type Communications (massive MCT), whichconnects multiple devices and objects so as to provide various servicesregardless of time and place, is also one of the most important issuesthat are to be considered in the next generation communication.Moreover, discussions are made on services/terminals (or user equipment(UE)) that are sensitive to reliability and latency. And, discussionsare made on the adoption of a next generation radio access technologythat is based on the enhanced mobile broadband communication, massiveMTC, Ultra-Reliable and Low Latency Communication (URLLC), and so on.And, for convenience, the corresponding technology will be referred toas a new RAT or NR.

FIG. 4 illustrates a system structure of a new generation radio accessnetwork (NG-RAN) to which NR is applied.

Referring to FIG. 4 , the NG-RAN may include a gNB and/or an eNBproviding a user plane and a control plane protocol termination to aterminal. FIG. 4 illustrates a case of including only the gNB. The gNBand eNB are connected to each other by an Xn interface. The gNB and eNBare connected to a 5G Core Network (5GC) through an NG interface. Morespecifically, the gNB and eNB are connected to the access and mobilitymanagement function (AMF) through an NG-C interface and connected to auser plane function (UPF) through an NG-U interface.

FIG. 5 illustrates functional partitioning between NG-RAN and 5GC.

Referring to FIG. 5 , the gNB may provide inter-cell radio resourcemanagement (RRM), radio bearer (RB) control, connection mobilitycontrol, radio access control, measurement configuration & provision,dynamic resource allocation, and the like. An AMF may provide functionssuch as NAS security, idle state mobility handling, and the like. A UPFmay provide functions such as mobility anchoring, PDU handling, and thelike. A session management function (SMF) may provide functions such asUE IP address allocation, PDU session control, and the like.

FIG. 6 illustrates a frame structure applicable in NR.

Referring to FIG. 6 , a frame may consist of 10 milliseconds (ms) andmay include 10 subframes of 1 ms.

A subframe may include one or a plurality of slots according tosubcarrier spacing.

Table 1 below shows subcarrier spacing configuration μ.

TABLE 1 μ Δf = 2^(μ) · 15 [kHz] CP(Cyclic prefix) 0 15 Normal 1 30Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal

Table 2 below shows the number of slots in a frame (N^(frameμ) _(slot)),the number of slots in a subframe (N^(subframeμ) _(slot)), and thenumber of symbols in a slot (N^(slot) _(symb)) according to thesubcarrier spacing configuration μ.

TABLE 2 μ N_(symb) ^(slot) N_(slot) ^(frame, μ) N_(slot) ^(subframe, μ)0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

FIG. 6 shows μ=0, 1, and 2.

A physical downlink control channel (PDCCH) may include one or morecontrol channel elements (CCEs) as shown in Table 3 below.

TABLE 3 Aggregation level Number of CCEs 1 1 2 2 4 4 8 8 16 16

In other words, the PDCCH may be transmitted through a resourceincluding 1, 2, 4, 8 or 16 CCEs. Here, the CCE includes six resourceelement groups (REGs), and one REG includes one resource block in thefrequency domain and one orthogonal frequency division multiplexing(OFDM) symbol in the time domain. Meanwhile, in the NR, a new unitcalled a control resource set (CORESET) may be introduced. A UE mayreceive the PDCCH in the CORESET.

FIG. 7 illustrates a CORESET.

Referring to FIG. 7 , the CORESET may include N^(CORESET) _(RB) resourceblocks in the frequency domain and N^(CORESET) _(symb) ∈{1, 2, 3}symbols in the time domain. N^(CORESET) _(RB)and N^(CORESET) _(symb) maybe provided by a base station (BS) through higher layer signaling. Asshown in FIG. 7 , a plurality of CCEs (or REGs) may be included in theCORESET.

The UE may attempt to detect a PDCCH in units of 1, 2, 4, 8 or 16 CCEsin the CORESET. One or a plurality of CCEs for attempting PDCCHdetection may be referred to as PDCCH candidates.

A plurality of CORESETs may be configured for the UE.

FIG. 8 is a view illustrating a difference between a legacy controlregion and a CORESET in the NR.

Referring to FIG. 8 , a control region 800 in the legacy wirelesscommunication system (e.g., LTE/LTE-A) is configured in the entiresystem band used by a BS. All terminals, excluding some UEs that supportonly a narrow band (e.g., eMTC/NB-IoT terminals), were supposed to beable to receive wireless signals of the entire system band of the BS inorder to properly receive/decode control information transmitted fromthe BS.

Meanwhile, in the NR, the aforementioned CORESET was introduced.CORESETs (801, 802, 803) may be radio resources for control informationthat the UE should receive and may use only a part of the system band,not the entire system band. The BS may allocate the CORESET to eachterminal, and may transmit control information through the allocatedCORESET. For example, in FIG. 8 , a first CORESET (801) may be allocatedto UE 1, a second CORESET (802) may be allocated to UE 2, and a thirdCORESET (803) may be allocated to UE 3. The UE in the NR may receive thecontrol information from the BS even if the UE does not necessarilyreceive the entire system band.

The CORESET may include a UE-specific CORESET for transmittingUE-specific control information and a common CORESET for transmittingcontrol information common to all UEs.

Meanwhile, in the NR, high reliability may be required depending on anapplication field, and in this context, a target block error rate (BLER)for a downlink control information (DCI) transmitted through a downlinkcontrol channel (e.g., physical downlink control channel (PDCCH)) may besignificantly lower than that of the related art. As an example of amethod for satisfying the requirement for such high reliability, theamount of contents included in the DCI may be reduced and/or the amountof resources used in DCI transmission may be increased. Here, theresource may include at least one of a resource in the time domain, aresource in the frequency domain, a resource in a code domain, and aresource in a spatial domain.

The following technologies/characteristics may be applied to NR.

<Self-contained Subframe Structure>

FIG. 9 illustrates an example of a frame structure for the new radioaccess technology (new RAT).

In NR, as a purpose for minimizing latency, as shown in FIG. 9 , astructure having a control channel and a data channel being processedwith Time Division Multiplexing (TDM), within one TTI, may be consideredas one type of frame structure.

In FIG. 9 , an area marked with slanted lines represents a downlinkcontrol area, and an area marked in black represents an uplink controlarea. An area marked in black may be used for downlink (DL) datatransmission or may be used for uplink (UL) data transmission. Thecharacteristic of such structure is that, since downlink (DL)transmission and uplink (UL) transmission are carried out sequentially,DL data is sent out (or transmitted) from a subframe, and ULAcknowledgement/Not-acknowledgement (ACK/NACK) may also be received inthe subframe. As a result, time needed until data retransmission, when adata transmission error occurs, may be reduced, and, accordingly,latency in the final data transfer (or delivery) may be minimized

In the above-described data and control TDMed subframe structure, a timegap is needed for a transition process (or shifting process) from atransmission mode to a reception mode of the base station and UE, or atransition process (or shifting process) from a reception mode to atransmission mode of the base station and UE. For this, in aself-contained subframe structure, some of the OFDM symbols of a timepoint where a transition from DL to UL occurs may be configured as aguard period (GP).

<Analog Beamforming #1>

In a Millimeter Wave (mmW), since the wavelength becomes short,installation of multiple antenna elements on a same surface becomespossible. That is, on a 30 GHz band, the wavelength is 1 cm, therebyenabling installation of a total of 100 antenna elements to be performedon a 5 by 5 cm panel in a 2-dimension (2D) alignment format at intervalsof 0.5 wavelength (lambda). Therefore, in mmW, coverage shall beextended or throughput shall be increased by increasing beamforming (BF)gain using multiple antenna elements.

In this case, when a Transceiver Unit (TXRU) is provided so as to enabletransport power and phase adjustment to be performed per antennaelement, independent beamforming per frequency resource may beperformed. However, there lies a problem of reducing effectiveness inlight of cost in case of installing TXRU to all of the 100 or moreantenna elements. Therefore, a method of mapping multiple antennaelements to one TXRU and adjusting beam direction by using an analogphase shifter is being considered. Since such analog beamforming methodcan only form a single beam direction within a full band, it isdisadvantageous in that in cannot provide frequency selectivebeamforming.

As an intermediate form of digital beamforming (digital BF) and analogbeamforming (analog BF), hybrid beamforming (hybrid BF) having B numberof TXRUs, which is less than Q number of antenna elements, may beconsidered. In this case, although there are differences according toconnection methods between the B number of TXRUs and the Q number ofantenna elements, a direction of a beam that may be transmittedsimultaneously shall be limited to B or below.

<Analog Beamforming #2>

In an NR system, in case multiple antennas are used, the usage of ahybrid beamforming method, which is a combination of digital beamformingand analog beamforming, is rising. At this point, analog beamforming isadvantageous in that it performs precoding (or combining) at an RF end,thereby reducing the number of RF chains and the number of D/A (or A/D)converters as well as achieving a performance that is proximate todigital beamforming. For simplicity, the hybrid beamforming structuremay be expressed as N number of TXRUs and M number of physical channels.Accordingly, digital beamforming for L number of data layers that are tobe transmitted by the transmitter may be expressed as an N by L matrix.Then, after the converted N number of digital signals pass through theTXRU so as to be converted to analog signals, analog beamforming, whichis expressed as an M by N matrix, is applied thereto.

FIG. 10 is an abstract diagram of a hybrid beamforming structure in theviewpoints of the TXRU and physical antenna.

In FIG. 10 , a number of digital beams is equal to L, and a number ofanalog beams is equal to N. Moreover, NR systems are considering asolution for supporting more efficient beamforming to a UE, which islocated in a specific area, by designing the base station to be capableof changing beamforming to symbol units. Furthermore, in FIG. 10 , whenspecific N number of TXRUs and M number of RF antennas are defined as asingle antenna panel, a solution of adopting multiple antenna panelscapable of having independent hybrid beamforming applied thereto isbeing considered in the NR system.

As described above, in case the base station uses multiple analog beams,since the analog beams that are advantageous for signal reception per UEmay vary, for at least the synchronization signal, system information,paging, and so on, a beam sweeping operation is being considered.Herein, the beam sweeping operation allows the multiple analog beamsthat are to be applied by the base station to be changed per symbol sothat all UEs can have reception opportunities.

FIG. 11 is a schematic diagram of the beam sweeping operation for asynchronization signal and system information during a downlink (DL)transmission process.

In FIG. 11 , a physical resource (or physical channel) through whichsystem information of the NR system is being transmitted by abroadcasting scheme is referred to as a physical broadcast channel(xPBCH). At this point, analog beams belonging to different antennapanels within a single symbol may be transmitted simultaneously. And, inorder to measure a channel per analog beam, as shown in FIG. 11 , asolution of adopting a beam reference signal (beam RS, BRS), which is areference signal (RS) being transmitted after having a single analogbeam (corresponding to a specific antenna panel) applied thereto. TheBRS may be defined for multiple antenna ports, and each antenna port ofthe BRS may correspond to a single analog beam. At this point, unlikethe BRS, a synchronization signal or xPBCH may be transmitted, afterhaving all analog beams within an analog beam group applied thereto, soas to allow a random UE to successfully receive the signal.

FIG. 12 shows examples of 5G usage scenarios to which the technicalfeatures of the present specification can be applied. The 5G usagescenarios shown in FIG. 12 are only exemplary, and the technicalfeatures of the present specification can be applied to other 5G usagescenarios which are not shown in FIG. 12 .

Referring to FIG. 12 , the three main requirements areas of 5G include(1) enhanced mobile broadband (eMBB) domain, (2) massive machine typecommunication (mMTC) area, and (3) ultra-reliable and low latencycommunications (URLLC) area. Some use cases may require multiple areasfor optimization and, other use cases may only focus on only one keyperformance indicator (KPI). 5G is to support these various use cases ina flexible and reliable way.

eMBB focuses on across-the-board enhancements to the data rate, latency,user density, capacity and coverage of mobile broadband access. The eMBBaims ˜10 Gbps of throughput. eMBB far surpasses basic mobile Internetaccess and covers rich interactive work and media and entertainmentapplications in cloud and/or augmented reality. Data is one of the keydrivers of 5G and may not be able to see dedicated voice services forthe first time in the 5G era. In 5G, the voice is expected to beprocessed as an application simply using the data connection provided bythe communication system. The main reason for the increased volume oftraffic is an increase in the size of the content and an increase in thenumber of applications requiring high data rates. Streaming services(audio and video), interactive video and mobile Internet connectivitywill become more common as more devices connect to the Internet. Many ofthese applications require always-on connectivity to push real-timeinformation and notifications to the user. Cloud storage andapplications are growing rapidly in mobile communication platforms,which can be applied to both work and entertainment. Cloud storage is aspecial use case that drives growth of uplink data rate. 5G is also usedfor remote tasks on the cloud and requires much lower end-to-end delayto maintain a good user experience when the tactile interface is used.In entertainment, for example, cloud games and video streaming areanother key factor that increases the demand for mobile broadbandcapabilities. Entertainment is essential in smartphones and tabletsanywhere, including high mobility environments such as trains, cars andairplanes. Another use case is augmented reality and informationretrieval for entertainment. Here, augmented reality requires very lowlatency and instantaneous data amount.

mMTC is designed to enable communication between devices that arelow-cost, massive in number and battery-driven, intended to supportapplications such as smart metering, logistics, and field and bodysensors. mMTC aims ˜years on battery and/or ˜1 million devices/km². mMTCallows seamless integration of embedded sensors in all areas and is oneof the most widely used 5G applications. Potentially by 2020, IoTdevices are expected to reach 20.4 billion. Industrial IoT is one of theareas where 5G plays a key role in enabling smart cities, assettracking, smart utilities, agriculture and security infrastructures.

URLLC will make it possible for devices and machines to communicate withultra-reliability, very low latency and high availability, making itideal for vehicular communication, industrial control, factoryautomation, remote surgery, smart grids and public safety applications.URLLC aims ˜1 ms of latency. URLLC includes new services that willchange the industry through links with ultra-reliability/low latency,such as remote control of key infrastructure and self-driving vehicles.The level of reliability and latency is essential for smart gridcontrol, industrial automation, robotics, drone control andcoordination.

Next, a plurality of use cases included in the triangle of FIG. 12 willbe described in more detail.

5G can complement fiber-to-the-home (FTTH) and cable-based broadband (orDOCSIS) as a means of delivering streams rated from hundreds of megabitsper second to gigabits per second. This high speed can be required todeliver TVs with resolutions of 4 K or more (6 K, 8 K and above) as wellas virtual reality (VR) and augmented reality (AR). VR and ARapplications include mostly immersive sporting events. Certainapplications may require special network settings. For example, in thecase of a VR game, a game company may need to integrate a core serverwith an edge network server of a network operator to minimize delay.

Automotive is expected to become an important new driver for 5G, withmany use cases for mobile communications to vehicles. For example,entertainment for passengers demands high capacity and high mobilebroadband at the same time. This is because future users will continueto expect high-quality connections regardless of their location andspeed. Another use case in the automotive sector is an augmented realitydashboard. The driver can identify an object in the dark on top of whatis being viewed through the front window through the augmented realitydashboard. The augmented reality dashboard displays information thatwill inform the driver about the object's distance and movement. In thefuture, the wireless module enables communication between vehicles,information exchange between the vehicle and the supportinginfrastructure, and information exchange between the vehicle and otherconnected devices (e.g., devices accompanied by a pedestrian). Thesafety system allows the driver to guide the alternative course ofaction so that he can drive more safely, thereby reducing the risk ofaccidents. The next step will be a remotely controlled vehicle orself-driving vehicle. This requires a very reliable and very fastcommunication between different self-driving vehicles and betweenvehicles and infrastructure. In the future, a self-driving vehicle willperform all driving activities, and the driver will focus only ontraffic that the vehicle itself cannot identify. The technicalrequirements of self-driving vehicles require ultra-low latency andhigh-speed reliability to increase traffic safety to a level notachievable by humans.

Smart cities and smart homes, which are referred to as smart societies,will be embedded in high density wireless sensor networks. Thedistributed network of intelligent sensors will identify conditions forcost and energy-efficient maintenance of a city or house. A similarsetting can be performed for each home. Temperature sensors, windows andheating controllers, burglar alarms and appliances are all wirelesslyconnected. Many of these sensors typically require low data rate, lowpower and low cost. However, for example, real-time HD video may berequired for certain types of devices for monitoring.

The consumption and distribution of energy, including heat or gas, ishighly dispersed, requiring automated control of distributed sensornetworks. The smart grid interconnects these sensors using digitalinformation and communication technologies to collect and act oninformation. This information can include supplier and consumerbehavior, allowing the smart grid to improve the distribution of fuel,such as electricity, in terms of efficiency, reliability, economy,production sustainability, and automated methods. The smart grid can beviewed as another sensor network with low latency.

The health sector has many applications that can benefit from mobilecommunications. Communication systems can support telemedicine toprovide clinical care in remote locations. This can help to reducebarriers to distance and improve access to health services that are notcontinuously available in distant rural areas. It is also used to savelives in critical care and emergency situations. Mobile communicationbased wireless sensor networks can provide remote monitoring and sensorsfor parameters such as heart rate and blood pressure.

Wireless and mobile communications are becoming increasingly importantin industrial applications. Wiring costs are high for installation andmaintenance. Thus, the possibility of replacing a cable with a wirelesslink that can be reconfigured is an attractive opportunity in manyindustries. However, achieving this requires that wireless connectionsoperate with similar delay, reliability, and capacity as cables and thattheir management is simplified. Low latency and very low errorprobabilities are new requirements that need to be connected to 5G.

Logistics and freight tracking are important use cases of mobilecommunications that enable tracking of inventory and packages anywhereusing location-based information systems. Use cases of logistics andfreight tracking typically require low data rates, but require a largerange and reliable location information.

Hereinafter, a discussion related to power saving will be described.

The terminal's battery life is a factor of the user experience thatinfluences the adoption of 5G handsets and/or services. Power efficiencyfor 5G NR terminals is not worse than at least LTE, and a study ofterminal power consumption may be provided in order to identify andapply techniques and designs for improvement.

ITU-R defines energy efficiency as one of the minimum technicalperformance requirements of IMT-2020. According to the ITU-R report,e.g. the minimum requirements related to the technical performance ofthe IMT-2020 air interface, the energy efficiency of a device can berelated to support for two aspects: a) efficient data transmission inthe loaded case, b) low energy consumption when there is no data.Efficient data transmission in the loaded case is demonstrated byaverage spectral efficiency. In the absence of data, low energyconsumption can be estimated by the sleep rate.

Since the NR system can support high-speed data transmission, it isexpected that user data will be burst and serviced for a very shortperiod of time. One efficient terminal power saving mechanism is totrigger the terminal for network access from the power efficiency mode.Unless there is information about network access through the terminalpower saving framework, the terminal maintains a power efficiency modesuch as a micro-sleep or OFF period within a long DRX period. Instead,when there is no traffic to be transmitted, the network may support theterminal to switch from the network access mode to the power saving mode(e.g., dynamic terminal switching to sleep with a network supportsignal).

In addition to minimizing power consumption with a newwake-up/go-to-sleep mechanism, it may be provided to reduce powerconsumption during network access in RRC_CONNECTED mode. In LTE, morethan half of the power consumption of the terminal occurs in theconnected mode. Power saving techniques should focus on minimizing themain factors of power consumption during network access, includingprocessing of aggregated bandwidth, dynamic number of RF chains anddynamic transmission/reception time and dynamic switching to powerefficiency mode. In most cases of LTE field TTI, there is no data orthere is little data, so a power saving scheme for dynamic adaptation toother data arrivals should be studied in the RRC-CONNECTED mode. Dynamicadaptation to traffic of various dimensions such as carrier, antenna,beamforming and bandwidth can also be studied. Further, it is necessaryto consider how to enhance the switching between the network connectionmode and the power saving mode. Both network-assisted andterminal-assisted approaches should be considered for terminal powersaving mechanisms.

The terminal also consumes a lot of power for RRM measurement. Inparticular, the terminal must turn on the power before the DRX ON periodfor tracking the channel to prepare for RRM measurement. Some of the RRMmeasurement is not essential, but consumes a lot of terminal power. Forexample, low mobility terminals do not need to be measured as frequentlyas high mobility terminals. The network may provide signaling to reducepower consumption for RRM measurement, which is unnecessary for theterminal. Additional terminal support, for example terminal stateinformation, etc., is also useful for enabling the network to reduceterminal power consumption for RRM measurement.

Accordingly, there is a need for research to identify the feasibilityand advantages of a technology that enables the implementation of aterminal capable of operating while reducing power consumption.

Hereinafter, UE power saving schemes will be described.

For example, the terminal power saving techniques may consider a powersaving signal/channel/procedure for triggering terminal adaptation totraffic and power consumption characteristics, adaptation to frequencychanges, adaptation to time changes, adaptation to the antenna,adaptation to the DRX configuration, adaptation to terminal processingcapabilities, adaptation to obtain PDCCH monitoring/decoding reduction,terminal power consumption adaptation and a reduction in powerconsumption in RRM measurement.

Regarding adaptation to the DRX configuration, a downlink shared channel(DL-SCH) featuring support for terminal discontinuous reception (DRX)for enabling terminal power saving, PCH featuring support for terminalDRX enabling terminal power saving (here, the DRX cycle may be indicatedto the terminal by the network) and the like may be considered.

Regarding adaptation to the terminal processing capability, thefollowing techniques may be considered. When requested by the network,the terminal reports at least its static terminal radio accesscapability. The gNB may request the ability of the UE to report based onband information. If allowed by the network, a temporary capabilitylimit request may be sent by the terminal to signal the limitedavailability of some capabilities (e.g., due to hardware sharing,interference or overheating) to the gNB. Thereafter, the gNB can confirmor reject the request. Temporary capability limitations must betransparent to 5GC. That is, only static functions are stored in 5GC.

Regarding adaptation to obtain PDCCH monitoring/decoding reduction, thefollowing techniques may be considered. The UE monitors the PDCCHcandidate set at a monitoring occasion configured in one or moreCORESETs configured according to a corresponding search spaceconfiguration. CORESET consists of a set of PRBs having a time intervalof 1 to 3 OFDM symbols. Resource units REG and CCE are defined inCORESET, and each CCE consists of a set of REGs. The control channel isformed by a set of CCEs. Different code rates for the control channelare implemented by aggregating different numbers of CCEs. Interleavedand non-interleaved CCE-REG mapping is supported in CORESET.

Regarding the power saving signal/channel/procedure for triggeringterminal power consumption adaptation, the following technique may beconsidered. In order to enable reasonable terminal battery consumptionwhen carrier aggregation (CA) is configured, an activation/deactivationmechanism of cells is supported. When one cell is deactivated, the UEdoes not need to receive a corresponding PDCCH or PDSCH, cannot performa corresponding uplink transmission, and does not need to perform achannel quality indicator (CQI) measurement. Conversely, when one cellis activated, the UE must receive the PDCH and PDCCH (if the UE isconfigured to monitor the PDCCH from this SCell), and is expected to beable to perform CQI measurement. The NG-RAN prevents the SCell of thesecondary PUCCH group (the group of SCells in which PUCCH signaling isassociated with the PUCCH of the PUCCH SCell) from being activated whilethe PUCCH SCell (secondary cell composed of PUCCH) is deactivated. TheNG-RAN causes the SCell mapped to the PUCCH SCell to be deactivatedbefore the PUCCH SCell is changed or removed.

When reconfiguring without mobility control information, the SCell addedto the set of serving cells is initially deactivated, and the (unchangedor reconfigured) SCells remaining in the set of serving cells do notchange the activate state (e.g. active or inactive).

SCells are deactivated when reconfiguring with mobility controlinformation (e.g., handover).

In order to enable reasonable battery consumption when BA (bandwidthadaptation) is configured, only one uplink BWP and one downlink BWP oronly one downlink/uplink BWP pair for each uplink carrier may beactivated at once in the active serving cell, and all other BWPsconfigured in the terminal are deactivated. In deactivated BWPs, the UEdoes not monitor the PDCCH and does not transmit on the PUCCH, PRACH andUL-SCH.

For BA, the terminal's reception and transmission bandwidth need not beas wide as the cell's bandwidth and can be adjusted: the width can becommanded to change (e.g. shrink during periods of low activity to savepower), position in the frequency domain can be moved (e.g. to increasescheduling flexibility), the subcarrier spacing can be ordered to change(e.g., to allow different services). A subset of the total cellbandwidth of a cell is referred to as a bandwidth part (BWP), the BA isobtained by configuring the BWP(s) to the UE and knowing that it iscurrently active among the BWPs configured to the UE. When the BA isconfigured, the terminal only needs to monitor the PDCCH on one activeBWP. That is, there is no need to monitor the PDCCH on the entiredownlink frequency of the cell. The BWP inactive timer (independent ofthe DRX inactive timer described above) is used to convert the activeBWP to the default BWP: tyhe timer is restarted when the PDCCH decodingsucceeds, switching to the default BWP occurs when the timer expires.

FIG. 13 illustrates a scenario in which three different bandwidth partsare configured.

FIG. 13 shows an example in which BWP1, BWP2, and BWP3 are configured ontime-frequency resources. BWP1 has a width of 40 MHz and a subcarrierspacing of 15 kHz, BWP2 has a width of 10 MHz and a subcarrier spacingof 15 kHz, and BWP3 may have a width of 20 MHz and a subcarrier spacingof 60 kHz. In other words, each of the bandwidth parts may havedifferent widths and/or different subcarrier spacings.

Regarding the power consumption reduction in RRM measurement, thefollowing technique may be considered. If two measurement types arepossible, the RRM configuration may include the beam measurementinformation related to the SSB(s) (for layer 3 mobility) and theCSI-RS(s) for the reported cell(s). In addition, when CA is configured,the RRM configuration may include a list of best cells on each frequencyfor which measurement information is available. In addition, the RRMmeasurement information may include beam measurement for listed cellsbelonging to the target gNB.

The following techniques can be used in various wireless access systemssuch as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, and the like. CDMA may beimplemented with a radio technology such as Universal Terrestrial RadioAccess (UTRA) or CDMA2000. TDMA may be implemented with a radiotechnology such as Global System for Mobile communications (GSM)/GeneralPacket Radio Service (GPRS)/Enhanced Data Rates for GSM Evolution(EDGE). OFDMA may be implemented with a wireless technology such as IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and Evolved UTRA(E-UTRA). UTRA is a part of Universal Mobile Telecommunications System(UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution(LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA, and Advanced(LTE-A)/LTE-A pro is an evolved version of 3GPP LTE. 3GPP New Radio orNew Radio Access Technology (NR) is an evolved version of 3GPPLTE/LTE-A/LTE-A pro.

For clarity, the description is based on a 3GPP communication system(e.g., LTE-A, NR), but the technical idea of the present specificationis not limited thereto. LTE refers to technology after 3GPP TS 36.xxxRelease 8. In detail, LTE technology after 3GPP TS 36.xxx Release 10 isreferred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13is referred to as LTE-A pro. 3GPP NR refers to the technology after TS38.xxx Release 15. LTE/NR may be referred to as a 3GPP system. “xxx”means standard document detail number. LTE/NR may be collectivelyreferred to as a 3GPP system. Background art, terms, abbreviations, andthe like used in the description of the present specification may referto matters described in standard documents published before the presentspecification.

Hereinafter, the proposal of the present specification will be describedin more detail.

Additional advantages, objects and features of the present specificationwill be partially described in the following description, it will beapparent to one of ordinary skill in the art or will be able to learn inpart from the practice of this specification upon review of thefollowing. Objects and other advantages of the present specification canbe realized and achieved by the accompanying drawings, as well as thestructures particularly pointed out in the claims and claims of thepresent specification.

Cross-slot scheduling can reduce power consumption by reducingunnecessary PDSCH buffering and the like.

However, due to the location of monitoring occasions by a plurality ofsearch space sets, monitoring of common information monitored by aplurality of terminals (i.e. a plurality of user equipments (UEs)) etc.,the power saving performance of the cross-slot scheduling may be greatlyreduced.

For example, if a monitoring occasion of different search space setsconfigured with a minimum K0 (Here, K0 may mean a slot offset betweenthe DCI and the PDSCH linked to the DCI (e.g., the PDSCH scheduled bythe DCI)) of 1 is located in contiguous slots, it is not possible toswitch to a micro sleep due to the monitoring occasion, or there may bea case in which the actual power saving of the UE does not operate, suchas a case where the PDSCH scheduled by the previous monitoring occasionmay be located in a micro sleep period due to another monitoringoccasion.

In order to reduce the power consumption of the UE, 3GPP conducted apower saving study item, and SI conducted a study on cross-slotscheduling as one of the power saving schemes. An example of cross-slotscheduling may be described below through a drawing.

FIG. 14 schematically shows an example of cross-slot scheduling.

According to FIG. 14 , the UE may perform a reception of PDCCH (DCI)1410 in slot #n. The terminal may perform a micro sleep 1430 (or alow-power PDCCH reception operation using a low voltage, low clockspeed, etc.) in a period in which the PDSCH is guaranteed not to betransmitted. Thereafter, the UE may perform reception 1420 of a PDSCHrelated to a PDCCH (DCI) in slot #m (corresponding to a resource and/orregion) indicated by the received PDCCH (DCI).

The following shows a method and procedure for reducing powerconsumption in cross-slot scheduling (discussed in the correspondingSI).

Minimum K0>0 and the aperiodic CSI-RS triggering offset is not withinthe duration—the terminal can switch to micro-sleep after PDCCHreception—no added PDSCH and CSI-RS signal reception within a givenduration (e.g., the same slot).

-   -   Known to the UE when decoding the PDCCH    -   Reduction of PDCCH processing within extended micro sleep time        and reduced terminal power consumption    -   In order to avoid the need for fast PDCCH processing, a minimum        K0>0 is essential.    -   Terminal assistant information may be considered

A general procedure for a terminal saving scheme when cross-slotscheduling is used.

-   -   gNB semi-statically configures the TDRA to the terminal        according to the terminal capability    -   All scheduleable TDRA value(s) are K0≥X and K2∝X (here, X>0) (or        guarantees that only values larger than X among K0/K2 values of        the TDRA table are scheduled)    -   Determination of the X value may be affected by BWP switching        triggered by, for example, DCI (if supported, with cross-slot        scheduling)    -   All aperiodic CSI-RS triggering offset(s) are not less than the        X value    -   The terminal decodes the PDCCH and retrieves the index of the        scheduleable TDRA value.    -   The terminal can enter micro sleep after receiving the last        PDCCH symbol    -   The terminal processes the PDSCH at the start time indicated        from the TDRA value

As can be seen from the above, cross-slot scheduling can be used forpower saving purposes, the network indicates the minimum K0 to the UE(here, K0 represents a slot offset between the DCI and the PDSCHassociated with the DCI, for example, when K0=1, this means that thePDSCH is transmitted to the next slot of the slot in which the PDCCH wastransmitted). The UE switches to micro sleep for a period of timeguaranteed by a minimum K0 after PDCCH reception (precisely, the lastsymbol of the corresponding CORESET), thereby reducing power consumptiondue to PDSCH buffering and the like.

The same operation may be applied to K2, and K2 denotes a slot offsetbetween the DCI and the PUSCH associated with the DCI. Accordingly, theK0 operation described in the present specification may be applied tothe K2 operation as long as it does not contradict the concept of thespecification.

In this specification, a method of efficiently reducing powerconsumption of a UE using cross-slot scheduling is proposed.

In the present specification, the minimum K0 value configured by thenetwork may fall back to the existing K0 value by signaling of thenetwork or by using a timer or the like (At this time, the existing K0value may be interpreted as 0 or the minimum value among the K0 valuesof the configured TDRA table).

This specification may be implemented by the TDRA table configured bythe RRC signaling and signaling for whether the power saving mode isapplied or not (by RRC, L1, or MAC CE). That is, when instructed toapply the power saving mode, K0 of the smallest value in the TDRA tablesignaled by RRC is regarded as the minimum K0 in the followingspecification, and the following specification can be applied. (This maymean that the minimum K0 is not additionally signaled, and the UEconsiders the smallest value of K0 in the TDRA table signaled in advanceas the minimum K0 discussed in this specification.)

For example, if the minimum K0 in the TDRA table indicated by RRC is 1,the network may inform whether or not the power saving mode is appliedthrough RRC, L1, or MAC CE signaling, and when the UE is instructed toapply the power saving mode, it is assumed that the minimum K0 is 1 inthe following specification and the UE may perform a power savingoperation by applying the scheme proposed below.

In case that such a scheme is applied, the UE performs buffering for thePDSCH when there is no indication for the minimum K0 (for power savingpurposes) with respect to the TDRA table signaled for each bandwidthpart (BWP), and PDSCH buffering may be skipped based on the minimumvalue among K0 in the corresponding TDRA table when there is anindication for the minimum K0.

In addition, in the present specification, the minimum K0 is describedbased on a case where it is determined by implicit determination or isdynamically indicated by L1 or MAC CE signaling, but the minimum K0 maybe also determined by RRC signaling, accordingly, the followingspecification may also be applied when the minimum K0 configured by RRCsignaling is used. In addition, when a semi-static configuration such asRRC signaling is used, whether or not the RRC signaled minimum K0 isapplied for dynamic adaptation may be signaled by L1 or MAC CE.

In addition, in the following specification, power saving by PDSCHbuffering is discussed, but the PDSCH buffering-related operationproposed below can also be applied to downlink signal buffering inpreparation for aperiodic CSI-RS transmission.

For example, when the minimum K0 is 1, it may be assumed that there isno transmission of an aperiodic CSI-RS linked to the corresponding PDCCHin a slot monitoring the PDCCH. For example, when a minimum K0 is usedfor power saving, that is, when PDSCH buffering is not performed withina period guaranteed by the minimum K0, it may be assumed that there isno aperiodic CSI-RS transmission in the corresponding region.

In the present specification, the description is mainly based on K0(e.g. the number of slots (number, the same hereinafter) between thePDCCH and the scheduled PDSCH, or the delay between the DL grant and thecorresponding DL data (PDSCH) reception), but the present specificationmay be applied to K1 (e.g. the number of slots between PDSCH scheduledin PDCCH and associated PUCCH, or

the delay between the DL data (PDSCH) reception and the correspondingACK (acknowledgement) transmission on the UL) and/or K2 (e.g. the numberof slots between the PDCCH and the scheduled PUSCH, or the delay betweenthe UL data (PUSCH) transmission and the UL grant in the DL) as well asK0 in the same manner.

<Indication of Minimum K0>

The minimum K0 can be indicated as follows. The options below can beimplemented alone or in combination.

1. Option 1) Multiple Time Domain Resource Allocation (TDRA) table andimplicit minimum K0

-   -   The smallest K0 value of each table is assumed to be the        smallest K0    -   Determining the default TDRA table (predefined or network        indication)

Hereinafter, this option will be described in more detail.

Currently, the TDRA table may be configured for each BWP, and multipleTDRA table(s) may be configured for each BWP for power saving usingcross-slot scheduling. In this case, the minimum K0 value in each TDRAtable may be implicitly determined as the minimum K0 when thecorresponding table is used.

The network may indicate a minimum K0 for cross-slot scheduling, or mayindicate one of a plurality of TDRA tables (dynamically using a powersaving signal or the like).

When the UE receives the minimum K0 signal, it can be assumed that theTDRA table associated with the minimum K0 is activated, and when theTDRA table is signaled, whether to perform PDSCH buffering may bedetermined based on the minimum K0 of the corresponding TDRA table.

In addition, when multiple TDRA table(s) are configured, it is suggestedto define a default TDRA table in advance or to be configured by thenetwork. In this case, when the minimum K0 is not configured, thedefault TDRA table may be used for the purpose of an ambiguity period ofminimum K0 signaling, a fallback operation for a power saving scheme,and the like.

2. Option 2) Explicit signaling for minimum K0 indication

As another method, the network may configure the TDRA table as beforeand directly indicate the minimum K0 value. In this case, the UE canoperate as follows.

Alt 1) Among the K0 on the table, only the indicated minimum K0 orhigher is valid.

In the TDRA table, it can be assumed that it is valid only for K0 thatis greater than or equal to the minimum K0 configured by the network.This may mean that PDSCH buffering is not performed in the periodguaranteed by the configured minimum K0.

Alt 2) Create a new K0 by adding the minimum K0 to each K0 value in theconfigured table.

It can be assumed that the minimum K0 value configured by the networkmeans an offset to the K0 value on the TDRA table. That is, when theminimum K0 is signaled from the network to the UE, the UE may update theTDRA table by adding the signaled minimum K0 value to the K0 value ofthe existing TDRA table.

Alt 3) Apply Alt 2 only to K0=0 rows on the table

The method of adding the offset of Alt 2 can be applied only tocontent(s) satisfying a specific condition (in the TDRA table). Forexample, when the offset is signaled, the signaled offset may be addedonly to content(s) that satisfy the condition of K0=0 among thepreviously configured TDRA content(s).

<Configurations of Cross-slot Scheduling for Power Saving>

Hereinafter, a method for increasing a power saving gain by cross-slotscheduling will be described.

1. Configuring the application interval of the minimum K0

-   -   Opt 1) Indicate the interval to which the signaled minimum K0 is        applied    -   Opt 2) Introduce the timer to determine when minimum K0 is        released

As mentioned above, cross-slot scheduling can reduce power consumptionby reducing unnecessary PDSCH buffering. However, due to the location ofa monitoring occasion by a plurality of search space sets, monitoring ofcommon information monitored by a plurality of UEs, etc., the powersaving performance of cross-slot scheduling may be greatly reduced.

For example, if the monitoring occasions of different search space setsconsisting of a minimum K0 of 1 are located in consecutive slots, thetransition to micro sleep is not possible due to the monitoringoccasion, or, there may be a case in which the actual power saving ofthe UE does not operate, such as a case where a PDSCH scheduled by aprevious monitoring occasion may be located in a micro sleep period dueto another monitoring occasion.

In the present specification, when cross-slot scheduling is used forpower saving, it is proposed to use the following method to increase thepower saving gain. The following methods can be implemented alone or incombination.

Additionally, the following methods may be applied only when the minimumK0 value is 1 or more. This may include a case where the networkconfigures a minimum K0 value and the corresponding value is 1 or more,as well as a case where the minimum K0 value in the TDRA tableconfigured for a specific BWP is 1 or more. (This may mean that aspecific BWP is used for power saving purposes, and may be interpretedas recognizing that the power saving operation is applied to the UEconfigured to switch to the corresponding BWP.) The following schemescan be applied not only to cross-slot scheduling, but also to otherschemes of power saving schemes (e.g., CDRX operation, PDCCH monitoringadaptation, BWP/CA operation).

In addition, since the following operations are defined for the purposeof power saving, there may be a system impact in terms of schedulingflexibility and scheduling availability (e.g., blocking).

Therefore, in the present specification, it is proposed to configure theinterval to which the minimum K0 is applied together with the minimumK0, or to determine the release time of the minimum K0 using a timer orthe like, this can be commonly applied to the case of using the minimumK0 (in other words, a case that guarantees the PDSCH buffering skip ofthe UE for a specific period) as well as the following method(s). It mayalso operate in conjunction with the DRX status in the DRX operation.

For example, it may be assumed that the validity period of the minimumK0 and/or the minimum K0 is applied only to the on-duration in the DRX.This may mean that the validity period of the minimum K0 and/or theminimum K0 is not applied (e.g., perform default operation) in theperiod in which the inactivity timer, which is started when receiving anactual PDCCH in DRX operation, is operated.

2. Method 1) Search space set configuration(s) for power saving

-   -   Separately configuring a search space set for normal power mode        and a search space set for reduced power mode

More specifically, when a search space set configuration for powersaving operation is instructed and it is determined that the powersaving operation is applied (eg, when a minimum K0 is configured), theUE may apply a corresponding search space set configuration.

In order to increase the power saving gain, the network can beconfigured to position the monitoring occasion of the (all or part)search space set at the beginning (e.g., first 3 symbol(s)) of each slotin the configuration of the search space set for power saving purposes.The monitoring period of each search space set may be configured to begreater than the minimum K0.

Such a configuration is preferably avoided because it may cause sideeffects such as increasing blocking between search space sets andincreasing monitoring skips due to overlap of different CORESETs in ageneral situation. However, when power saving is required, it may bedesirable to reduce power consumption compared to schedulingflexibility.

For such an operation, the network may indicate the configuration of thesearch space set in the normal power mode and the configuration thesearch space set in the reduced power mode for each search space sets(or a specific search space set). The UE may select/apply a search spaceset configuration according to the power mode. The present specificationmay be applied only to an active BWP currently operating.

This can also be implemented in a manner in which monitoring isperformed only for a specific search space set(s) when a minimum K0 isconfigured and applied.

For example, if the minimum K0 is configured, the UE may monitor onlyfor a monitoring occasion located within 3 symbol(s) from the start ofthe slot or may perform monitoring only for a search space set in whichthe monitoring period is larger than the configured minimum K0.

3. Method 2) PDCCH monitoring periodicity adaptation depending onminimum K0

-   -   If the monitoring period of the search space set currently being        monitored is less than the minimum K0, increasing the monitoring        period of the SS (search space) set.

More specifically, when the PDCCH monitoring period is shorter than theperiod according to the minimum K0, the power saving gain due to theminimum K0 may be reduced because the PDCCH monitoring is performed inthe micro sleep period.

In order to solve such a problem, in the present specification, aminimum K0 value is configured, and when the monitoring period of thecurrently monitored search space set is shorter than the minimum K0period, it is proposed to increase the monitoring period.

This may be automatically applied when there is a monitoring occasiondue to a monitoring period within a micro sleep period by a minimum K0,and/or it may be implemented by a method of configuring a monitoringperiod of a related search space set together when configuring theminimum K0 value.

When the monitoring periodicity is implicitly changed by the minimum K0value, the new monitoring periodicity may be determined by apredetermined rule. (For example, it may be changed to twice the currentmonitoring periodicity, etc., and this may be interpreted as performingonly monitoring for an even-numbered (or odd-numbered) opportunity amongthe current monitoring occasions.)

4. Method 3) Skip PDCCH monitoring

-   -   Skip monitoring for another monitoring occasion located within        the minimum K0 from the monitoring occasion.

As another method, a method of skipping monitoring for a monitoringoccasion located within a micro sleep period by a minimum K0 may beused.

This may be applied to each search space set, or may be applied evenwhen a monitoring occasion of another search space set is located in amicro sleep period (that is, the interval guaranteed that there is noPDSCH transmission by the minimum (minimum) K0) of a specific searchspace set(s).

As an example, the network may configure a minimum K0 value for aspecific search space set, and the network may instruct not only tomonitor the search space set, but also to skip monitoring other searchspace sets within the interval determined by the minimum K0 value fromeach monitoring occasion of the corresponding search space set.

5. Meanwhile,

The methods for increasing power saving efficiency using cross-slotscheduling proposed above can be applied in the same way even when aduration is applied to the search space set. In the search space setconfiguration in the specification, “duration” is defined as “a durationof Ts<ks slots indication a number of slots that the search space setsexists by duration”, where ks means monitoring periodicity. .

That is, it means that the UE monitors the search space set in ks slotsper monitoring periodicity for the search space set for which theduration is configured.

Accordingly, when it is necessary to monitor the search space setcorresponding to each slot within the duration, the power saving effectdue to cross-slot scheduling may be reduced. Therefore, the method(s)proposed above may be applied to a slot within a duration.

For example, when a minimum K0 (for power saving) is configured by thenetwork, when power saving is applied, and/or when the interval betweenmonitoring slots within the duration is less than the minimum K0, themethods 1, 2 and/or 3 proposed above, such as monitoring periodicityadjustment and/or monitoring skip, can be applied to slots within aduration.

<Exceptional Cases of Micro Sleep by Cross-slot Scheduling>

In actual network coverage, a UE that requires power saving and a UEthat does not need it, and/or a UE capable of power saving operation anda UE that is not capable of power saving may exist at the same time.

In this case, the power saving operation for a specific UE group mayresult in a decrease in overall system performance In the presentspecification, in order to reduce the system impact, it is proposed toperform PDSCH buffering regardless of whether the minimum K0 or not inthe following cases. (Or, regardless of whether the minimum K0 or not,PDSCH buffering may be performed based on the minimum K0 value (or K0=0)in the configured TDRA table.)

Individually or through a combination, each of the following cases maybe defined as an exceptional case(s) for micro sleep (or PDSCHbuffering).

Case 1) the case where SI-RNTI is monitored in Type 0 CSS, the UE mayperform PDSCH buffering assuming that K0 is 0 regardless of the minimumK0.

Case 2) the case where SI-RNTI, RA-RNTI, TC-RNTI, and P-RNTI aremonitored in Type0A CSS, Type1 CSS, Type1 CSS, and Type2 CSSrespectively and the case where pdsch-ConfigCommon does not containpdsch-TimeDomainAllocationList (i.e. the case using the default TDRAtable)

Case 3) the case where C-RNTI, MCS-C-RNTI, CS-RNTI are monitored in CSSlinked to CORESET other than CORESET#0 or monitored in USS and the casewhere pdsch-ConfigCommon and/or pdsch-Config does not includepdsch-TimeDomainAllocationList (i.e. when using the default TDRA table)

Case 4) the case where C-RNTI, MCS-C-RNTI, CS-RNTI are monitored incandidates monitoring SI-RNTI, RA-RNTI and/or P-RNTI for the followingreasons and the case where the search space set uses the default TDRAtable

More specifically, the case where the following configurations areprovided to the terminal:

-   -   One or more search space sets corresponding to one or more        ‘searchSpaceZero’, ‘searchSpaceSIB1’,        ‘searchSpaceOtherSystemInformation’, ‘pagingSearchSpace’ and/or        ‘ra-SearchSpace’, and/or    -   C-RNTI, MCS-C-RNTI, or a CS-RNTI,

The UE may monitor the PDCCH candidate(s) for DCI format 0_0 and DCI 1_0with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI in one or moresearch space sets in the slot. Here, the above slot may be a slot inwhich the UE monitors PDCCH candidate(s) for at least DCI format 0_0 orDCI format 1_0 with CRC scrambled by SI-RNTI, RA-RNTI, or P-RNTI.

Case 5) the case where the K0 value (e.g. K0=0) less than the minimum K0is included in the TDRA table for the search space set monitoringbroadcast (or group common) information (e.g., all or part of SI-RNTI,RA-RNTI, P-RNTI, SFI-RNTI): It means that the PDSCH buffering isperformed based on the corresponding K0 value (for example, immediatelyperformed after receiving PDCCH) when there is a case in which K0 (e.g.,K0=0) smaller than the minimum K0 is included in the corresponding tableeven if the default TDRA table is not used and the TDRA table isconfigured through RRC signaling (e.g., SIB, UE-dedicated signaling).

That is, if a value smaller than the dynamically indicated minimum K0exists in the TDRA table configured for the corresponding search spaceset (i.e., a search space set that monitors broadcast (or group common)information), the corresponding value may also be applied.

The exceptional case may be defined for each case listed above, orsimply, when the default TDRA table is applied, it may be assumed thatthe minimum K0 configured by the NW is not applied to the monitoring forthe corresponding search space set.

On the other hand, exceptional cases may be defined for each case listedabove, or simply, when a default TDRA table (e.g., a table forapplicable PDSCH time domain resource allocation) is applied, it may beassumed that the minimum K0 configured by the NW is not applied to themonitoring of the corresponding search space set.

Hereinafter, as an embodiment of the above-described case, a feature inwhich the minimum K0 is not applied (based on the use of the defaultTDRA) will be described with reference to the drawings. The followingdrawings are prepared to describe a specific example of the presentspecification. Since the names of specific devices or names of specificsignals/messages/fields described in the drawings are provided by way ofexample, the technical features of the present specification are notlimited to the specific names used in the following drawings.

FIG. 15 is a flowchart of a method for receiving a PDSCH based on adefault PDSCH time domain resource allocation according to an embodimentof the present specification.

According to FIG. 15 , the terminal may receive downlink controlinformation from the base station (S1510). Here, the downlink controlinformation may include minimum applicable scheduling offsetinformation, and the minimum applicable scheduling offset informationmay indicate a minimum applicable slot offset. In other words, theterminal may receive downlink control information indicating the minimumapplicable slot offset.

The minimum applicable slot offset may mean a minimum K0 described later(and described above) and described above (and described later). And,the minimum K0 may be expressed as K0min.

The terminal may receive the PDSCH from the base station on a slothaving a slot offset value equal to or greater than the minimumapplicable slot offset value (S1520).

In FIG. 15 , a basic structure of a PDSCH reception method based on thedefault PDSCH time domain resource allocation in the presentspecification has been described. Hereinafter, an example in FIG. 15will be described in another way through the drawings.

FIG. 16 is a flowchart of a method for receiving a PDSCH based on adefault PDSCH time domain resource allocation according to anotherembodiment of the present specification.

According to FIG. 16 , the terminal may receive minimum applicable slotoffset candidate information from the base station (S1610).

Here, the minimum applicable slot offset candidate information mayinclude a plurality of minimum applicable slot offset candidates. Here,for example, the minimum applicable slot offset candidate informationmay be ‘minimumSchedulingOffset’ to be described later. In other words,for example, the minimum applicable slot offset candidate informationmay be ‘minimumSchedulingOffsetK0’ and/or ‘minimumSchedulingOffsetK2’,which will be described later. Here, the example of the minimumapplicable slot offset candidate information is only an example of thepresent specification. That is, the minimum applicable slot offsetcandidate information may be implemented by other embodiments of thepresent specification described above (and/or to be described later).

The terminal may receive downlink control information from the basestation (S1620). Here, the downlink control information may includeminimum applicable scheduling offset information. Here, the minimumapplicable scheduling offset information may inform one minimumapplicable slot offset candidate among a plurality of minimum applicableslot offset candidates as the minimum applicable slot offset.

That is, here, for example, the downlink control information may includeminimum applicable scheduling offset information indicating a minimumapplicable slot offset.

In this case, the minimum applicable scheduling offset information maybe 0 bits or 1 bit.

For example, when ‘minimumSchedulingOffset (minimum scheduling offset)’corresponding to the upper layer parameter is not configured, theminimum applicable scheduling offset may be 0 bits.

Also, for example, when ‘minimumSchedulingOffset’ corresponding to anupper layer parameter is configured, the minimum applicable schedulingoffset may be 1 bit. In this case, the 1-bit indicator may be used todetermine the minimum applicable slot offset (e g minimum applicableK0). (On the other hand, this content can also be applied to the minimumapplicable K2.)

Here, with respect to ‘minimumSchedulingOffset’, ‘PDSCH-Config’transmitted through RRC signaling may include‘minimumSchedulingOffsetK0’, and the ‘PDSCH-Config’ transmitted throughRRC signaling may include ‘minimumSchedulingOffsetK2’.

For example, as shown in Table 4 below, ‘PDSCH-Config’ and‘minimumSchedulingOffsetK0’ above may be defined in the followingformat.

TABLE 4 -- ASN1START -- TAG-PDSCH-CONFIG-START PDSCH-Config ::= SEQUENCE { ......  [[  maxMIMO-Layers-r16   INTEGER (1..8) OPTIONAL, --Need M  minimumSchedulingOffsetK0-r16   SetupRelease {MinSchedulingOffsetK0-Values- r16 }  OPTIONAL -- Need M  ]] ......MinSchedulingOffsetK0-Values-r16 ::=  SEQUENCE (SIZE(1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER(0..maxK0-SchedulingOffset-r16) -- TAG-PDSCH-CONFIG-STOP -- ASN1STOP

Here,'minimumSchedulingOffsetK0' may mean a list of minimum K0 values.Here, the minimum K0 parameter may represent the minimum applicablevalue(s) for the TDRA table for the PDSCH (and/or the A-CSI RStriggering offset). The minimum applicable K0 and/or the minimumapplicable K2 may be indicated based on the table below. Table 5 belowis a table of joint indications of the minimum applicable schedulingoffset K0/K2.

TABLE 5 When ‘minimumSchedulingOffset’ When ‘minimumSchedulingOffset’ isconfigured for DL BWP, is configured for UL BWP, Bit field minimumapplicable K0 for active minimum applicable K2 for active mapped toindex DL BWP UL BWP 0 First value configured by First value configuredby ‘minimumSchedulingOffset’ for the ‘minimumSchedulingOffset’ for theactive DL BWP active UL BWP 1 The second value configured by The secondvalue configured by ‘minimumSchedulingOffset’ for the‘minimumSchedulingOffset’ for the active DL BWP when the second activeUL BWP when the second value is set; value is set; otherwise, 0otherwise, 0

Here, the minimum applicable slot offset may be a slot offset related toexpecting the UE to receive the PDSCH based on at least one slot offsethaving a value greater than or equal to the minimum applicable slotoffset. (That is, the UE may receive the PDSCH based on a slot offsethaving a value greater than or equal to the minimum applicable slotoffset.) In other words, the minimum applicable slot offset may be aslot offset related to the UE not expecting to receive the PDSCH basedon at least one slot offset having a value smaller than the minimumapplicable slot offset. (That is, the terminal may not receive the PDSCHbased on a slot offset having a value smaller than the minimumapplicable slot offset.) In this case, the minimum applicable slotoffset may mean a minimum K0 described above (and will be describedlater). And, the minimum K0 may be expressed as K0min.

In other words, S1620 may be described as a different expression, (viadownlink control information (DCI)), the UE may receive an indication ofthe minimum applicable K0 (in other words, the minimum applicable K0value) from the base station. Here, for example, one or two minimumapplicable K0 candidate values are indicated by RRC, and the minimumapplicable K0 value to be actually applied is determined by DCI. And, anew minimum applicable K0 value may be applied from a slot in which anapplication delay has passed since the DCI is received.

The terminal may receive the PDSCH from the base station on a slothaving a slot offset value equal to or greater than the minimumapplicable slot offset value (S1630). Here, when the UE receives thePDSCH, it is not necessary to apply the previously received minimumapplicable slot offset.

Returning to FIG. 15 again, for example, the terminal may not apply theminimum applicable slot offset based on the default PDSCH time domainresource allocation being used.

More specifically, based on a default PDSCH time domain resourceallocation being used and a PDSCH transmission being scheduled with acell-radio network temporary identity (C-RNTI), a configuredscheduling-RNTI (CS-RNTI) or a modulation and coding scheme-cell-RNTI(MCS-C-RNTI) in a common search space associated with a control resourceset (CORESET) 0, the UE may not apply the minimum applicable slotoffset.

Or, for example, based on a default PDSCH time domain resourceallocation being used and a PDSCH transmission being scheduled with acell-radio network temporary identity (C-RNTI), a configuredscheduling-RNTI (CS-RNTI) or a modulation and coding scheme-cell-RNTI(MCS-C-RNTI) in a UE specific search space (USS) and a common searchspace associated with a control resource set (CORESET) except for aCORESET 0, the UE may not apply the minimum applicable slot offset.

Here, for example, the UE may receive the PDSCH based on the defaultPDSCH time domain resource allocation without applying the minimumapplicable slot offset. In this case, the terminal may receive the PDSCHbased on the slot offset defined in the default PDSCH time domainresource allocation (e.g., default PDSCH time domain resource allocationin Tables 6 to 10 to be described later, etc.). Meanwhile, the terminalmay receive the PDSCH after a slot has passed by the value of the slotoffset from the slot in which the DCI is received.

As an example, when the minimum applicable slot offset is applied, theterminal may not expect to receive the PDSCH based on a slot offsethaving a value smaller than a value of a minimum applicable slot offset.

As an example, the terminal receives minimum scheduling offsetinformation from the base station, the minimum applicable schedulingoffset information may be information indicating one of values in theminimum scheduling offset information as the minimum applicable slotoffset value. Here, the terminal may receive the minimum schedulingoffset information based on higher layer signaling.

For example, the downlink control information is DCI format 1_1, and theDCI format 1_1 may be used for scheduling the PDSCH.

Summarizing the above and describing it differently, the terminal mayreceive the downlink control information from the base station. Theterminal may receive a physical downlink shared channel (PDSCH) from thebase station based on the downlink control information. Here, thedownlink control information may include minimum applicable schedulingoffset information indicating a minimum applicable slot offset. Inaddition, here, the minimum applicable slot offset may be an offsetrelated to the UE not expecting to receive the PDSCH based on a slotoffset having a value greater than or equal to the minimum applicableslot offset.

The content of FIG. 15 may be described in another way as follows.

The exceptional cases 1, 2, 3, and 4 proposed above can be defined usingthe table of the existing specification. The table below may be includedin the specification, and it defines whether to assume the default TDRAtable or the RRC signaled TDRA table for the RNTI and the search spaceset in which the corresponding RNTI is monitored. Therefore, whendefining cases 1,2,3,4 as exceptional cases, it is proposed to assumethat there is no buffering skip by the minimum K0 indicated forcross-slot scheduling in the combination of an RNTI and a search space(SS) set corresponding to the highlighted area of the table below.

In other words, it is suggested that “The adaptation on the minimumapplicable value of K0” indicated by the network is not applied in thecase indicated in the table below (i.e., the case specified to use thedefault TDRA table in Table 5 below). (Or, some of the cases highlightedin the table below can be defined as exceptional cases)

Table 6 below corresponds to an example of the applicable PDSCH timedomain resource allocation.

TABLE 6 SS/PBCH pdsch- pdsch- block and ConfigCommon Config PDSCH TimePDCCH CORESET contains pdsch- contains pdsch- domain resource searchmultiplexing TimeDomainAl- TimeDomainAl- allocation to RNTI spacepattern locationList locationList apply SI-RNTI Type 0 1 — — Default Afor common normal CP 2 — — Default B 3 — — Default C SI-RNTI Type 0A 1No — Default A common 2 No — Default B 3 No — Default C 1, 2, 3 Yes —pdsch- TimeDomainAl- locationList provided in pdsch- ConfigCommonRA-RNTI, Type 1 1, 2, 3 No — Default A MsgB-RNTI, common 1, 2, 3 Yes —pdsch- TC-RNTI TimeDomainAl- locationList provided in pdsch-ConfigCommon P-RNTI Type 2 1 No — Default A common 2 No — Default B 3 No— Default C 1, 2, 3 Yes — pdsch- TimeDomainAl- locationList provided inpdsch- ConfigCommon C-RNTI, Any common 1, 2, 3 No — Default AMCS-C-RNTI, search space 1, 2, 3 Yes — pdsch- CS-RNTI related toTimeDomainAl- CORESET 0 locationList provided in pdsch- ConfigCommonC-RNTI, Any common 1, 2, 3 No No Default A MCS-C-RNTI, search space 1,2, 3 Yes No pdsch- CS-RNTI not related to TimeDomainAl- CORESET 0locationList UE specific provided in pdsch- search space ConfigCommon 1,2, 3 No/Yes Yes pdsch- TimeDomainAl- locationList provided in pdsch-Config

That is, as an example in Table 6, in a common search space associatedwith CORESET (control resource set) 0, based on the PDSCH transmissionbeing scheduled with cell-radio network temporary identity (C-RNTI),configured scheduling-RNTI (CS-RNTI) or MCS-C-RNTI (modulation andcoding scheme-cell-RNTI), and based on the default PDSCH time domainresource allocation being used (e.g., default A in Table 6), theterminal may not apply the minimum applicable slot offset. In addition,for example, in a UE specific search space (USS) and a common searchspace associated with a CORESET other than CORESET (control resourceset) 0, based on the PDSCH transmission being scheduled with acell-radio network temporary identity (C-RNTI), configuredscheduling-RNTI (CS-RNTI) or modulation and coding scheme-cell-RNTI(MCS-C-RNTI), and based on the default PDSCH time domain resourceallocation being used (e.g., default A in Table 6), the terminal may notapply the minimum applicable slot offset.

In other words, if the default TDRA table is applied, adaptation for theminimum applicable value of K0 may not be applied to C/CS/MCS-RNTImonitored in the common search space (of type 0/0A/1/2) associated withCORESET 0.

Meanwhile, the applicable PDSCH time domain resource allocation in Table6 may be an applicable PDSCH time domain resource allocation related toDCI format 1_0 and DCI format 1_1. Here, the contents of the default A,the default B, and the default C in Table 6 may be the same as in Tables7 to 10 below.

The following Table 7 is an example of a default PDSCH time domainresource allocation A (i.e., default A) for a normal CP.

TABLE 7 Row dmrs-TypeA- PDSCH index Position mapping type K₀ S L 1 2Type A 0 2 12 3 Type A 0 3 11 2 2 Type A 0 2 10 3 Type A 0 3 9 3 2 TypeA 0 2 9 3 Type A 0 3 8 4 2 Type A 0 2 7 3 Type A 0 3 6 5 2 Type A 0 2 53 Type A 0 3 4 6 2 Type B 0 9 4 3 Type B 0 10 4 7 2 Type B 0 4 4 3 TypeB 0 6 4 8 2, 3 Type B 0 5 7 9 2, 3 Type B 0 5 2 10 2, 3 Type B 0 9 2 112, 3 Type B 0 12 2 12 2, 3 Type A 0 1 13 13 2, 3 Type A 0 1 6 14 2, 3Type A 0 2 4 15 2, 3 Type B 0 4 7 16 2, 3 Type B 0 8 4

The following Table 8 is an example of the default PDSCH time domainresource allocation A (i.e., default A) for the extended CP.

TABLE 8 Row dmrs-TypeA- PDSCH index Position mapping type K₀ S L 1 2Type A 0 2 6 3 Type A 0 3 5 2 2 Type A 0 2 10 3 Type A 0 3 9 3 2 Type A0 2 9 3 Type A 0 3 8 4 2 Type A 0 2 7 3 Type A 0 3 6 5 2 Type A 0 2 5 3Type A 0 3 4 6 2 Type B 0 6 4 3 Type B 0 8 2 7 2 Type B 0 4 4 3 Type B 06 4 8 2, 3 Type B 0 5 6 9 2, 3 Type B 0 5 2 10 2, 3 Type B 0 9 2 11 2, 3Type B 0 10 2 12 2, 3 Type A 0 1 11 13 2, 3 Type A 0 1 6 14 2, 3 Type A0 2 4 15 2, 3 Type B 0 4 6 16 2, 3 Type B 0 8 4

The following Table 9 is an example of the default PDSCH time domainresource allocation B (i.e., default B).

TABLE 9 Row dmrs-TypeA- PDSCH index Position mapping type K₀ S L 1 2, 3Type B 0 2 2 2 2, 3 Type B 0 4 2 3 2, 3 Type B 0 6 2 4 2, 3 Type B 0 8 25 2, 3 Type B 0 10 2 6 2, 3 Type B 1 2 2 7 2, 3 Type B 1 4 2 8 2, 3 TypeB 0 2 4 9 2, 3 Type B 0 4 4 10 2, 3 Type B 0 6 4 11 2, 3 Type B 0 8 4 12(Note 1) 2, 3 Type B 0 10 4 13 (Note 1) 2, 3 Type B 0 2 7 14 (Note 1) 2Type A 0 2 12 3 Type A 0 3 11 15 2, 3 Type B 1 2 4 16 Reserved

In the part indicated by note 1 in Table 9, when the PDSCH is scheduledas SI-RNTI in the PDCCH type 0 common search space, the UE may assumethat this PDSCH resource allocation is not applied. Table 10 below is anexample of the default PDSCH time domain resource allocation C (i.e.,default C).

TABLE 10 Row dmrs-TypeA- PDSCH index Position mapping type K₀ S L 1(Note 1) 2, 3 Type B 0 2 2 2 2, 3 Type B 0 4 2 3 2, 3 Type B 0 6 2 4 2,3 Type B 0 8 2 5 2, 3 Type B 0 10 2 6 Reserved 7 Reserved 8 2, 3 Type B0 2 4 9 2, 3 Type B 0 4 4 10 2, 3 Type B 0 6 4 11 2, 3 Type B 0 8 4 122, 3 Type B 0 10 4 13 (Note 1) 2, 3 Type B 0 2 7 14 (Note 1) 2 Type A 02 12 3 Type A 0 3 11 15 (Note 1) 2, 3 Type A 0 0 6 16 (Note 1) 2, 3 TypeA 0 2 6

In the part indicated by Note 1 in Table 10, when the PDSCH is scheduledas SI-RNTI in the PDCCH type 0 common search space, the UE may assumethat this PDSCH resource allocation is not used. Alternatively, for type0, 0A, 1, 2 CSS that monitors SI-, P-, and RA-RNTI specified in thetable above, it may be assumed that the cross-slot based power savingscheme based on the minimum K0 is not applied.

Regarding C-RNTI, assuming that the cross-slot based power saving schemeby minimum K0 is not applied to the C-RNTI monitored together with SI-,RA-, P-RNTI in Types 0, 0A, 1 and 2 mentioned above, and/or it may beassumed that a cross-slot-based power saving scheme based on a minimumK0 is applied in the remaining types of CSS and USS. Here, that thecross-slot-based power saving scheme based on the minimum K0 is appliedmeans a minimum K0 configuration, or whether buffering is performedaccording to the minimum K0.

<Search Space Set Specific Minimum K0>

As in the exceptional case suggested above, there may be a case where itis difficult to save power by the minimum K0. Another way to solve this,a method is proposed in which a network designates a search space set towhich a minimum K0 is applied, or a search space set (or CORESET) towhich a minimum K0 is applied by a predefined definition.

For example, the PDSCH buffering skip by the minimum K0 can be appliedonly to a specific search space type (e.g., CSS/USS) (or search spaceset (CORESET) of a specific index).

For example, the minimum K0 can be applied only to the USS. In the caseof CSS, a plurality of UEs may perform monitoring for the correspondingCSS, and among the corresponding UEs, UE(s) that do not need powersaving or cannot perform power saving operation may be included.Therefore, for CSS, the minimum K0 additionally signaled by the networkmay not be applied.

When the minimum K0 is configured as BWP specific, a set of searchspaces to which the minimum K0 is not applied may be defined in advanceor indicated by the network. For example, when the exceptional case(s)proposed in the present specification exists in a specific BWP, it maybe defined in advance that the minimum K0 is not applied to the case(s).

Similarly, whether to apply a minimum K0 may be determined according toa service type. For example, in the case of a URLLC service, a pluralityof monitoring opportunities for the same search space set within a slotmay be configured to reduce latency. In this case, a power saving schemeusing cross-slot scheduling may be inappropriate.

Accordingly, a service type to which a minimum K0 and a PDSCH bufferingskipping is applied (or not applied) may be determined according to apredefined definition in the specification or an indication of anetwork. This may be classified by a DCI format or the like. That is, ifthe DCI format (e.g., compact DCI) for URLLC is separately defined, theminimum K0 may not be applied to the search space set monitoring thecorresponding DCI format (or for candidates monitoring the DCI format).

<Minimum K0 and Buffering Skip>

The minimum K0 and whether to buffer may be independently determined.

For example, different search space sets monitored in the same slot mayhave different minimums K0. For example, for SI-RNTI monitored in CSS ofa specific slot, pdsch-TimeDomainAllocationList provided inpdsch-ConfigCommon is not signaled, so the minimum K0 is 0 assuming adefault TDRA table. With respect to the C-RNTI monitored in the USS ofthe same slot, the pdsch-TimeDomainAllocationList provided inpdsch-Config and the minimum K0 are signaled, and the signaled minimumK0 may be applied.

That is, a minimum K0 may assume different values for each RNTI and/orsearch space set. In this case, whether to buffer or not (or whether“The adaptation on the minimum applicable value of K0”) may bedetermined based on the smallest value among different minimum K0s inthe corresponding slot.

For example, if SI-RNTI and C-RNTI are monitored in different searchspace sets in the same slot as above and the minimum K0 is differentfrom each other (e.g., SI-RNTI→0, C-RNTI→2), whether to performbuffering (or whether “The adaptation on the minimum applicable value ofK0”) may be determined based on the smallest minimum K0 (e.g.,SI-RNTI→0). That is, when the minimum K0 for each SS set (RNTI in theexample below) monitored in the same slot is different, a minimum valuemay be applied.

As another example, different minimum K0s may be assumed for each RNTIin the same search space set. For example, if the DCI scrambling withSI-RNTI and C-RNTI in CSS not linked to CORESET#0 is monitored and theTDRA table is configured by pdsch-TimeDomainAllocationList provided inpdsch-Config, and if pdsch-TimeDomainAllocationList provided inpdsch-Config is not configured, SI-RNTI assumes a default TDRA table andC-RNTI follows the TDRA table given by RRC signaling.

In this case, when a minimum K0 for power saving is indicated, theSI-RNTI cannot assume a corresponding minimum K0, and the C-RNTI canassume a corresponding minimum K0. That is, in the same search spaceset, a minimum K0 to be assumed according to the RNTI may be differentlyconfigured.

In this situation, the UE should determine whether to buffer by assuminga smaller value among the minimum K0 for each RNTI. In the case of anexample, when the minimum K0 in the default TDRA table is 0, and theminimum K0 to be applied to the C-RNTI is 2, which is indicated by thenetwork (for power saving), the UE may determine whether to buffer basedon 0 which is a smaller value.

In addition, even if the minimum K0 for power saving is greater than 0,when buffering needs to be performed in the corresponding slot (becausethere is an RNTI with a minimum K0 of 0 or search space set), even inthe RNTI and/or search space set to which the minimum K0 (for powersaving) configured by the network is applied, it can be assumed that theminimum K0 is 0.

This is even if the network configures the minimum K0 (for power saving)greater than 0, when the UE assumes a minimum K0 of 0 in a specificslot, the network may mean that the same slot scheduling is possible fora search space set and/or an RNTI that may assume a minimum K0 greaterthan 0. When operating in this way, the network has the advantage ofavoiding scheduling restrictions such as delay, which may occur due tocross-slot scheduling, in the corresponding slot.

This specification may be expressed as follows. When there are multiplesearch space sets monitored by the terminal in a specific slot, or whenmonitoring PDCCH candidates for multiple RNTIs even within the samesearch space set, with regard to the terminal, for the minimum number ofTDRA K0 in the corresponding slot and/or the minimum number of slots upto the CSI-RS for CSI measurement indicated by the corresponding PDCCHand/or K2, the minimum K0 value of TDRA (e.g. default and/or commonand/or terminal-specific configured TDRA) in the corresponding slot maybe applied as an exception.

<Optimization of Cross-slot Scheduling Based Power Saving>

The cross-slot scheduling and power saving scheme using the minimum K0proposed above can obtain an additional power saving gain through thefollowing method.

The search space set configured to monitor SI-RNTI, P-RNTI, and RA-RNTIincludes time domain resource information for monitoring thecorresponding search space set using monitoring periodicity, offset, andthe like.

On the other hand, the RNTI does not need to perform monitoring at everymonitoring occasion. For example, whether or not to monitor eachinformation may be determined by the following information.

-   -   RACH

In response to the PRACH transmission, the UE may attempt to detect DCIformat 1_0 having a CRC scrambled by a corresponding RA-RNTI during awindow controlled by a higher layer.

The window above starts at the first symbol of the fastest CORESET, theterminal may be configured to receive the PDCCH for the Type 1-PDCCH CSSset which is at least one symbol after the last symbol of a PRACHoccasion corresponding to PRACH transmission. Here, the symbol durationmay correspond to the SCS of the Type 1-PDCCH CSS set.

The window length of the number of slots based on the SCS of the Type1-PDCCH CSS set may be provided by ra-ResponseWindow.

In other words, the (terminal) starts the ra-ResponseWindow composed ofRACH-ConfigCommon at the first PDCCH occasion from the end of the randomaccess preamble transmission. (The terminal) may monitor the PDCCH ofthe SpCell for the random access response(s) identified as RA-RNTI whilethe ra-ResponseWindow is running

-   -   Paging

In RRC_IDLE or RRC_INACTIVE, the UE may monitor the SI change indicationat its own paging occasion every DRX cycle.

When a common search space is provided to the active BWP in order tomonitor paging to the terminal, the terminal in RRC_CONNECTED maymonitor the SI change indication at a paging occasion at least onceevery modification period.

The ETWS or CMAS capable terminal in RRC_IDLE or RRC_INACTIVE maymonitor the indication for PWS notification in its own paging occasionevery DRX cycle.

When a common search space on an active BWP is provided to the terminalto monitor paging, the ETWS or CMAS capable terminal in RRC_CONNECTEDmay monitor the indication for PWS notification on a paging occasion atleast once every default paging cycle.

-   -   SI update

For example, when selecting a cell (e.g., when power is supplied), whenreselecting a cell, when returning from outside coverage, afterreconfiguration to complete synchronization, immediately after receivingan indication that system information has changed, after entering thenetwork from another RAT, immediately after receiving the PWSnotification and/or whenever the terminal does not have a valid versionof the stored SIB, the UE may need to apply the SI acquisitionprocedure.

Meanwhile, according to the above, it is possible to determine whetherto monitor RACH, paging, SI update, etc. according to a specific windowand a specific condition, this may mean that it is not necessary tomonitor the RNTI in all monitoring occasions configured in the searchspace set configuration.

Therefore, in the present specification, it is proposed that the minimumK0 (for power saving) indicated by the network is applied in the sectionexcluding the monitoring section defined in the spec.

For example, if SI-RNTI and C-RNTI are monitored in the same searchspace set among the above-described embodiments, and the minimum K0 foreach RNTI is different, it can be assumed that the minimum K0 of SI-RNTIis valid only within the interval defined in the above specification inthe example that the smallest minimum K0 is applied.

That is, the interval for monitoring the actual SI-RNTI among themonitoring occasions of the search space set is determined by thedefinition of the specification, and the minimum K0 applied to theC-RNTI may be applied in the remaining monitoring occasions. Throughthis, the UE can obtain additional power saving gain through nobuffering or the like.

<Error Handling for PS-PDCCH Misdetection>

Cross-slot scheduling using minimum K0/K2 is a method of reducing powerconsumption by not performing PDSCH buffering in the interval guaranteedby the minimum K0/K2 and/or slowly performing processing required forPDCCH decoding (e.g., using low voltage/low clock speed, etc.). In thiscase, the minimum K0/K2 may be configured using a PS-PDCCH or the like.

In this case, if the PS-PDCCH indicating the minimum K0/K2 cannot bedetected or misinterpreted due to a false-alarm, etc., the UE mayperform a malfunction such as failing to perform buffering for a periodin which the PDSCH is transmitted, and/or if the malfunction isprolonged, the throughput of the UE can be greatly reduced. In thisspecification, a fallback operation is proposed to solve such a problem.

-   -   Detection of missing/false alarm

The criterion for determining whether the UE has a missed/false alertfor the indicated minimum K0/K2 may be a case that satisfies all or partof the following conditions.

1. A case that the network indicates a value smaller than the minimumK0/K2 (instructed in advance by the network) in the time domain resourceallocation field in the DCI transmitted for PDSCH scheduling

A. For example, when the minimum K0/K2 is indicated as 2, but K0/K2corresponding to 0 or 1 is indicated in DCI scheduling the PDSCH

2. A case that the PDCCH is not found at the monitoring occasion for thePS-PDCCH (or the PDCCH/PDSCH including the corresponding information)indicating the minimum K0/K2 and/or a case that a value smaller than theminimum K0/K2 known by the UE is indicated by the DCI which is receivedafter the corresponding point in time and schedules the PDSCH

A. That is, when the above condition is satisfied in the DCI detectedwithin a certain time from the PS-PDCCH monitoring occasion, it may beassumed that the PS-PDCCH is missing or a false alarm.

3. A case that PDCCH/PDSCH reception was performed by applying thecorresponding value after receiving the minimum K0/K2 but PDSCH decodingfails more than X times (but PDCCH decoding was successful)

A. For example, if the PDCCH decoding succeeds, but thePDSCH/PUCCH/PUSCH transmission/reception with the minimum K0/K2 appliedfails X (here, X may be defined in advance or may be indicated throughhigher layer signaling of the network) times or more, the UE may assumethat the PS-PDCCH indicating the minimum K0/K2 has been missed or thatthe corresponding decoding is a false alarm.

4. When, among the rows of the TDRA table, one or more rows that can beapplied only in the normal mode and/or in the power saving mode areindicated to the UE by predefined or through higher layer signaling ofthe network, and if a row of the opposite mode is detected in DCI ineach mode, it can be assumed that the PS-PDCCH is a missed or falsealarm.

A. In this case, condition 2 above may be additionally considered. Thatis, when the above condition is satisfied in the DCI detected within acertain time from the PS-PDCCH monitoring occasion, it may be assumedthat the PS-PDCCH is missing or a false alarm.

-   -   Fallback behavior

When the UE detects a missed or false alarm for the minimum K0/K2indication by the method proposed above, it may perform a fallbackoperation as follows. The fallback operation may be performed throughone of the following methods or a combination of the methods proposedbelow.

1. The buffering operation can be performed assuming the minimum K0/K2in the current TDRA table, here, this may be a useful method whendistinguishing a row available in one TDRA table by a minimum K0/K2.

2. Alternatively, the minimum K0/K2 can be assumed to be a pre-definedvalue.

A. For example, a minimum K0/K2 value for fallback indicated by higherlayer signaling of the network (or predefined in the specification) maybe applied in the fallback operation.

For example, the exemplary embodiments of the present specificationdescribed so far may be described again from the viewpoint of theterminal as follows.

FIG. 17 is a flowchart of a method for receiving a PDSCH based on adefault PDSCH time domain resource allocation from a terminalperspective according to an embodiment of the present specification.

According to FIG. 17 , the terminal may receive minimum applicable slotoffset candidate information from the base station (S1710).

Here, the minimum applicable slot offset candidate information mayinclude a plurality of minimum applicable slot offset candidates.

The terminal may receive downlink control information from the basestation (S1720). Here, the downlink control information may includeminimum applicable scheduling offset information. Here, the minimumapplicable scheduling offset information may inform one minimumapplicable slot offset candidate among a plurality of minimum applicableslot offset candidates as the minimum applicable slot offset.

The terminal may receive the PDSCH from the base station on a slothaving a slot offset value equal to or greater than the minimumapplicable slot offset value (S1730).

Here, as described above, the downlink control information includesminimum applicable scheduling offset information indicating a minimumapplicable slot offset, and the minimum applicable slot offset is a slotoffset related to expecting the terminal to receive the PDSCH based onat least one slot offset having a value greater than or equal to theminimum applicable slot offset.

For example, the UE may not apply the minimum applicable slot offsetbased on a default PDSCH time domain resource allocation being used.

Here, for example, based on a default PDSCH time domain resourceallocation being used and a PDSCH transmission being scheduled with acell-radio network temporary identity (C-RNTI), a configuredscheduling-RNTI (CS-RNTI) or a modulation and coding scheme-cell-RNTI(MCS-C-RNTI) in a common search space associated with a control resourceset (CORESET) 0, the UE may not apply the minimum applicable slotoffset. Also, for example, the UE may receive the PDSCH based on thedefault PDSCH time domain resource allocation. Also, for example, the UEmay receive the PDSCH based on a slot offset defined in the defaultPDSCH time domain resource allocation. Also, for example, the UE mayreceive the PDSCH after a slot has passed by a value of the slot offsetfrom a slot on which the downlink control information is received.

For example, if the minimum applicable slot offset is applied, the UEmay not expect to receive the PDSCH based on a slot offset having avalue smaller than the value of the minimum applicable slot offset.

For example, the terminal receives minimum scheduling offset informationfrom the base station, the minimum applicable scheduling offsetinformation may be information indicating one of values in the minimumscheduling offset information as the minimum applicable slot offsetvalue.

Here, for example, the terminal may receive the minimum schedulingoffset information based on higher layer signaling.

For example, the downlink control information may be a downlink controlinformation (DCI) format 1_1, the DCI format 1_1 may be used forscheduling the PDSCH.

Since specific examples of the above embodiments are the same asdescribed above, in order to avoid unnecessary repetition, descriptionsof overlapping contents will be omitted.

FIG. 18 is a block diagram of an apparatus for receiving a PDSCH basedon a default PDSCH time domain resource allocation from a terminalperspective according to an embodiment of the present specification.

Referring to FIG. 18 , the processor 1800 may include a candidateinformation receiver 1810, a downlink control information receiver 1820,and a PDSCH receiver 1830. Here, the processor may correspond to theprocessor of FIGS. 21 to 27 .

The candidate information receiver 1810 may be configured to receiveminimum applicable slot offset candidate information from the basestation. Here, the minimum applicable slot offset candidate informationmay include a plurality of minimum applicable slot offset candidates.

The downlink control information receiver 1820 may be configured toreceive downlink control information from the base station. Here, thedownlink control information may include minimum applicable schedulingoffset information. Here, the minimum applicable scheduling offsetinformation may inform one minimum applicable slot offset candidateamong a plurality of minimum applicable slot offset candidates as theminimum applicable slot offset.

The PDSCH receiver 1830 may be configured to receive the PDSCH from thebase station on a slot having a slot offset value equal to or greaterthan the minimum applicable slot offset value.

Here, as described above, the downlink control information includesminimum applicable scheduling offset information indicating a minimumapplicable slot offset, and the minimum applicable slot offset is a slotoffset related to expecting the terminal to receive the PDSCH based onat least one slot offset having a value greater than or equal to theminimum applicable slot offset.

For example, the UE may not apply the minimum applicable slot offsetbased on a default PDSCH time domain resource allocation being used.

Here, for example, based on a default PDSCH time domain resourceallocation being used and a PDSCH transmission being scheduled with acell-radio network temporary identity (C-RNTI), a configuredscheduling-RNTI (CS-RNTI) or a modulation and coding scheme-cell-RNTI(MCS-C-RNTI) in a common search space associated with a control resourceset (CORESET) 0, the UE may not apply the minimum applicable slotoffset. Also, for example, the UE may receive the PDSCH based on thedefault PDSCH time domain resource allocation. Also, for example, the UEmay receive the PDSCH based on a slot offset defined in the defaultPDSCH time domain resource allocation. Also, for example, the UE mayreceive the PDSCH after a slot has passed by a value of the slot offsetfrom a slot on which the downlink control information is received.

For example, if the minimum applicable slot offset is applied, the UEmay not expect to receive the PDSCH based on a slot offset having avalue smaller than the value of the minimum applicable slot offset.

For example, the terminal receives minimum scheduling offset informationfrom the base station, the minimum applicable scheduling offsetinformation may be information indicating one of values in the minimumscheduling offset information as the minimum applicable slot offsetvalue.

Here, for example, the terminal may receive the minimum schedulingoffset information based on higher layer signaling.

For example, the downlink control information may be a downlink controlinformation (DCI) format 1_1, the DCI format 1_1 may be used forscheduling the PDSCH.

This example may be implemented as a chipset and/or a recording medium.

For example, an apparatus comprises at least one memory and at least oneprocessor being operatively connected to the at least one memory, here,the processor is configured to control a transceiver to receive, from abase station, downlink control information, the downlink controlinformation includes minimum applicable scheduling offset information,the minimum applicable scheduling offset information informs a minimumapplicable slot offset, and control the transceiver to receive, from thebase station, a physical downlink shared channel (PDSCH) on a slothaving a value of a slot offset equal to or greater than a value of theminimum applicable slot offset.

As another example, at least one computer readable medium (CRM) includesinstructions being executed by at least one processor, here, the atleast one processor is configured to control a transceiver to receive,from a base station, downlink control information, the downlink controlinformation includes minimum applicable scheduling offset information,the minimum applicable scheduling offset information informs a minimumapplicable slot offset, and control the transceiver to receive, from thebase station, a physical downlink shared channel (PDSCH) on a slothaving a value of a slot offset equal to or greater than a value of theminimum applicable slot offset.

Since specific examples of the above embodiments are the same asdescribed above, in order to avoid unnecessary repetition, descriptionsof overlapping contents will be omitted.

The example of the embodiments of the present specification described sofar may be described again from the viewpoint of the base station asfollows.

FIG. 19 is a flowchart of a method for transmitting a PDSCH based ondefault PDSCH time domain resource allocation from a base stationperspective according to an embodiment of the present specification.

FIG. 19 , the base station may transmit the minimum applicable slotoffset candidate information to the terminal (S1910). Here, the minimumapplicable slot offset candidate information may include a plurality ofminimum applicable slot offset candidates.

The base station may transmit downlink control information to theterminal (S1920). Here, the downlink control information may includeminimum applicable scheduling offset information. Here, the minimumapplicable scheduling offset information may inform one minimumapplicable slot offset candidate among the plurality of minimumapplicable slot offset candidates as the minimum applicable slot offset.

The base station may transmit the PDSCH to the terminal on a slot havinga slot offset value equal to or greater than the minimum applicable slotoffset value (S1930).

Here, as described above, the downlink control information includesminimum applicable scheduling offset information indicating a minimumapplicable slot offset, and the minimum applicable slot offset is a slotoffset related to expecting the terminal to receive the PDSCH based onat least one slot offset having a value greater than or equal to theminimum applicable slot offset.

For example, the UE may not apply the minimum applicable slot offsetbased on a default PDSCH time domain resource allocation being used.

Here, for example, based on a default PDSCH time domain resourceallocation being used and a PDSCH transmission being scheduled with acell-radio network temporary identity (C-RNTI), a configuredscheduling-RNTI (CS-RNTI) or a modulation and coding scheme-cell-RNTI(MCS-C-RNTI) in a common search space associated with a control resourceset (CORESET) 0, the UE may not apply the minimum applicable slotoffset. Also, for example, the UE may receive the PDSCH based on thedefault PDSCH time domain resource allocation. Also, for example, the UEmay receive the PDSCH based on a slot offset defined in the defaultPDSCH time domain resource allocation. Also, for example, the UE mayreceive the PDSCH after a slot has passed by a value of the slot offsetfrom a slot on which the downlink control information is received.

For example, if the minimum applicable slot offset is applied, the UEmay not expect to receive the PDSCH based on a slot offset having avalue smaller than the value of the minimum applicable slot offset.

For example, the terminal receives minimum scheduling offset informationfrom the base station, the minimum applicable scheduling offsetinformation may be information indicating one of values in the minimumscheduling offset information as the minimum applicable slot offsetvalue.

Here, for example, the terminal may receive the minimum schedulingoffset information based on higher layer signaling.

For example, the downlink control information may be a downlink controlinformation (DCI) format 1_1, the DCI format 1_1 may be used forscheduling the PDSCH.

Since specific examples of the above embodiments are the same asdescribed above, in order to avoid unnecessary repetition, descriptionsof overlapping contents will be omitted.

FIG. 20 is a block diagram of a PDSCH transmission apparatus based ondefault PDSCH time domain resource allocation from a base stationperspective according to an embodiment of the present specification.

Referring to FIG. 20 , the processor 2000 may include a candidateinformation transmission unit 2010, a downlink control informationtransmission unit 2020, and a PDSCH transmission unit 2030. Here, theprocessor may correspond to the processor of FIGS. 21 to 27 .

The candidate information transmission unit 2010 may be configured totransmit the minimum applicable slot offset candidate information to theterminal. Here, the minimum applicable slot offset candidate informationmay include a plurality of minimum applicable slot offset candidates.

The downlink control information transmission unit 2020 may beconfigured to transmit downlink control information to the terminal.Here, the downlink control information may include minimum applicablescheduling offset information. Here, the minimum applicable schedulingoffset information may inform one minimum applicable slot offsetcandidate among the plurality of minimum applicable slot offsetcandidates as the minimum applicable slot offset.

The PDSCH transmission unit 2030 may be configured to transmit the PDSCHto the terminal on a slot having a slot offset value equal to or greaterthan the minimum applicable slot offset value.

Here, as described above, the downlink control information includesminimum applicable scheduling offset information indicating a minimumapplicable slot offset, and the minimum applicable slot offset is a slotoffset related to expecting the terminal to receive the PDSCH based onat least one slot offset having a value greater than or equal to theminimum applicable slot offset.

For example, the UE may not apply the minimum applicable slot offsetbased on a default PDSCH time domain resource allocation being used.

Here, for example, based on a default PDSCH time domain resourceallocation being used and a PDSCH transmission being scheduled with acell-radio network temporary identity (C-RNTI), a configuredscheduling-RNTI (CS-RNTI) or a modulation and coding scheme-cell-RNTI(MCS-C-RNTI) in a common search space associated with a control resourceset (CORESET) 0, the UE may not apply the minimum applicable slotoffset. Also, for example, the UE may receive the PDSCH based on thedefault PDSCH time domain resource allocation. Also, for example, the UEmay receive the PDSCH based on a slot offset defined in the defaultPDSCH time domain resource allocation. Also, for example, the UE mayreceive the PDSCH after a slot has passed by a value of the slot offsetfrom a slot on which the downlink control information is received.

For example, if the minimum applicable slot offset is applied, the UEmay not expect to receive the PDSCH based on a slot offset having avalue smaller than the value of the minimum applicable slot offset.

For example, the terminal receives minimum scheduling offset informationfrom the base station, the minimum applicable scheduling offsetinformation may be information indicating one of values in the minimumscheduling offset information as the minimum applicable slot offsetvalue.

Here, for example, the terminal may receive the minimum schedulingoffset information based on higher layer signaling.

For example, the downlink control information may be a downlink controlinformation (DCI) format 1_1, the DCI format 1_1 may be used forscheduling the PDSCH.

Since specific examples of the above embodiments are the same asdescribed above, in order to avoid unnecessary repetition, descriptionsof overlapping contents will be omitted.

FIG. 21 shows an exemplary communication system (1), according to anembodiment of the present specification.

Referring to FIG. 21 , a communication system (1) to which variousembodiments of the present specification are applied includes wirelessdevices, Base Stations (BSs), and a network. Herein, the wirelessdevices represent devices performing communication using Radio AccessTechnology (RAT) (e.g., 5G New RAT (NR)) or Long-Term Evolution (LTE))and may be referred to as communication/radio/5G devices. The wirelessdevices may include, without being limited to, a robot (100 a), vehicles(100 b-1, 100 b-2), an eXtended Reality (XR) device (100 c), a hand-helddevice (100 d), a home appliance (100 e), an Internet of Things (IoT)device (100 f), and an Artificial Intelligence (AI) device/server (400).For example, the vehicles may include a vehicle having a wirelesscommunication function, an autonomous vehicle, and a vehicle capable ofperforming communication between vehicles. Herein, the vehicles mayinclude an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR devicemay include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality(MR) device and may be implemented in the form of a Head-Mounted Device(HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, asmartphone, a computer, a wearable device, a home appliance device, adigital signage, a vehicle, a robot, and so on. The hand-held device mayinclude a smartphone, a smartpad, a wearable device (e.g., a smartwatchor a smartglasses), and a computer (e.g., a notebook). The homeappliance may include a TV, a refrigerator, and a washing machine. TheIoT device may include a sensor and a smartmeter. For example, the BSsand the network may be implemented as wireless devices and a specificwireless device (200 a) may operate as a BS/network node with respect toother wireless devices.

The wireless devices (100 a-100 f) may be connected to the network (300)via the BSs (200). An Artificial Intelligence (AI) technology may beapplied to the wireless devices (100 a-100 f) and the wireless devices(100 a-100 f) may be connected to the AI server (400) via the network(300). The network (300) may be configured using a 3G network, a 4G(e.g., LTE) network, or a 5G (e.g., NR) network. Although the wirelessdevices (100 a-100 f) may communicate with each other through the BSs(200)/network (300), the wireless devices (100 a-100 f) may performdirect communication (e.g., sidelink communication) with each otherwithout passing through the BSs/network. For example, the vehicles (100b-1, 100 b-2) may perform direct communication (e.g., Vehicle-to-Vehicle(V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g.,a sensor) may perform direct communication with other IoT devices (e.g.,sensors) or other wireless devices (100 a-100 f).

Wireless communication/connections (150 a, 150 b, 150 c) may beestablished between the wireless devices (100 a-100 f)/BS (200), or BS(200)/BS (200). Herein, the wireless communication/connections may beestablished through various RATs (e.g., 5G NR) such as uplink/downlinkcommunication (150 a), sidelink communication (150 b) (or D2Dcommunication), or inter BS communication (150 c) (e.g., relay,Integrated Access Backhaul (IAB)). The wireless devices and the BSs/thewireless devices may transmit/receive radio signals to/from each otherthrough the wireless communication/connections (150 a, 150 b, 150 c).For example, the wireless communication/connections (150 a, 150 b, 150c) may transmit/receive signals through various physical channels. Forthis, at least a part of various configuration information configuringprocesses, various signal processing processes (e.g., channelencoding/decoding, modulation/demodulation, and resourcemapping/demapping), and resource allocating processes, fortransmitting/receiving radio signals, may be performed based on thevarious proposals of the present specification.

Meanwhile, in NR, multiple numerologies (or subcarrier spacing (SCS))for supporting various 5G services may be supported. For example, incase an SCS is 15 kHz, a wide area of the conventional cellular bandsmay be supported, and, in case an SCS is 30 kHz/60 kHz dense-urban,lower latency, and wider carrier bandwidth may be supported. In case theSCS is 60 kHz or higher, a bandwidth that is greater than 24.25 GHz maybe used in order to overcome phase noise.

An NR frequency band may be defined as two different types of frequencyranges (FR1, FR2). The values of the frequency ranges may be changed (orvaried), and, for example, the two different types of frequency ranges(FR1, FR2) may be as shown below in Table 11. Among the frequency rangesthat are used in an NR system, FR1 may mean a “sub 6 GHz range”, and FR2may mean an “above 6 GHz range” and may also be referred to as amillimeter wave (mmW).

TABLE 11 Frequency Range Corresponding designation frequency rangeSubcarrier Spacing FR1  450 MHz-6000 MHz  15, 30, 60 kHz FR2 24250MHz-52600 MHz 60, 120, 240 kHz

As described above, the values of the frequency ranges in the NR systemmay be changed (or varied). For example, as shown below in Table 12, FR1may include a band within a range of 410 MHz to 7125 MHz. Morespecifically, FR1 may include a frequency band of 6 GHz (or 5850, 5900,5925 MHz, and so on) and higher. For example, a frequency band of 6 GHz(or 5850, 5900, 5925 MHz, and so on) and higher being included in FR1may include an unlicensed band. The unlicensed band may be used forvarious purposes, e.g., the unlicensed band for vehicle-specificcommunication (e.g., automated driving).

TABLE 12 Frequency Range Corresponding designation frequency rangeSubcarrier Spacing FR1  410 MHz-7125 MHz  15, 30, 60 kHz FR2 24250MHz-52600 MHz 60, 120, 240 kHz

Hereinafter, an example of wireless devices to which the presentspecification is applied will be described in detail.

FIG. 22 shows an exemplary wireless device to which the presentspecification can be applied.

Referring to FIG. 22 , a first wireless device (100) and a secondwireless device (200) may transmit radio signals through a variety ofRATs (e.g., LTE, NR). Herein, {the first wireless device (100) and thesecond wireless device (200)} may correspond to {the wireless device(100 x) and the BS (200)} and/or {the wireless device (100 x) and thewireless device (100 x)} of FIG. 21 .

The first wireless device (100) may include one or more processors (102)and one or more memories (104) and additionally further include one ormore transceivers (106) and/or one or more antennas (108). Theprocessor(s) (102) may control the memory(s) (104) and/or thetransceiver(s) (106) and may be configured to implement thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document. For example, theprocessor(s) (102) may process information within the memory(s) (104) togenerate first information/signals and then transmit radio signalsincluding the first information/signals through the transceiver(s)(106). The processor(s) (102) may receive radio signals including secondinformation/signals through the transceiver (106) and then storeinformation obtained by processing the second information/signals in thememory(s) (104). The memory(s) (104) may be connected to theprocessor(s) (102) and may store various information related tooperations of the processor(s) (102). For example, the memory(s) (104)may store software code including instructions for performing a part orthe entirety of processes controlled by the processor(s) (102) or forperforming the descriptions, functions, procedures, proposals, methods,and/or operational flowcharts disclosed in this document. Herein, theprocessor(s) (102) and the memory(s) (104) may be a part of acommunication modem/circuit/chip designed to implement RAT (e.g., LTE orNR). The transceiver(s) (106) may be connected to the processor(s) (102)and transmit and/or receive radio signals through one or more antennas(108). Each of the transceiver(s) (106) may include a transmitter and/ora receiver. The transceiver(s) (106) may be interchangeably used withRadio Frequency (RF) unit(s). In the present specification, the wirelessdevice may represent a communication modem/circuit/chip.

The second wireless device (200) may include one or more processors(202) and one or more memories (204) and additionally further includeone or more transceivers (206) and/or one or more antennas (208). Theprocessor(s) (202) may control the memory(s) (204) and/or thetransceiver(s) (206) and may be configured to implement thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document. For example, theprocessor(s) (202) may process information within the memory(s) (204) togenerate third information/signals and then transmit radio signalsincluding the third information/signals through the transceiver(s)(206). The processor(s) (202) may receive radio signals including fourthinformation/signals through the transceiver(s) (206) and then storeinformation obtained by processing the fourth information/signals in thememory(s) (204). The memory(s) (204) may be connected to theprocessor(s) (202) and may store various information related tooperations of the processor(s) (202). For example, the memory(s) (204)may store software code including instructions for performing a part orthe entirety of processes controlled by the processor(s) (202) or forperforming the descriptions, functions, procedures, proposals, methods,and/or operational flowcharts disclosed in this document. Herein, theprocessor(s) (202) and the memory(s) (204) may be a part of acommunication modem/circuit/chip designed to implement RAT (e.g., LTE orNR). The transceiver(s) (206) may be connected to the processor(s) (202)and transmit and/or receive radio signals through one or more antennas(208). Each of the transceiver(s) (206) may include a transmitter and/ora receiver. The transceiver(s) (206) may be interchangeably used with RFtransceiver(s). In the present specification, the wireless device mayrepresent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices (100, 200) willbe described in more detail. One or more protocol layers may beimplemented by, without being limited to, one or more processors (102,202). For example, the one or more processors (102, 202) may implementone or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP,RRC, and SDAP). The one or more processors (102, 202) may generate oneor more Protocol Data Units (PDUs) and/or one or more Service Data Unit(SDUs) according to the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document. Theone or more processors (102, 202) may generate messages, controlinformation, data, or information according to the descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document. The one or more processors (102, 202) maygenerate signals (e.g., baseband signals) including PDUs, SDUs,messages, control information, data, or information according to thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document and provide thegenerated signals to the one or more transceivers (106, 206). The one ormore processors (102, 202) may receive the signals (e.g., basebandsignals) from the one or more transceivers (106, 206) and obtain thePDUs, SDUs, messages, control information, data, or informationaccording to the descriptions, functions, procedures, proposals,methods, and/or operational flowcharts disclosed in this document.

The one or more processors (102, 202) may be referred to as controllers,microcontrollers, microprocessors, or microcomputers. The one or moreprocessors (102, 202) may be implemented by hardware, firmware,software, or a combination thereof. As an example, one or moreApplication Specific Integrated Circuits (ASICs), one or more DigitalSignal Processors (DSPs), one or more Digital Signal Processing Devices(DSPDs), one or more Programmable Logic Devices (PLDs), or one or moreField Programmable Gate Arrays (FPGAs) may be included in the one ormore processors (102, 202). The descriptions, functions, procedures,proposals, methods, and/or operational flowcharts disclosed in thisdocument may be implemented using firmware or software and the firmwareor software may be configured to include the modules, procedures, orfunctions. Firmware or software configured to perform the descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document may be included in the one or more processors(102, 202) or stored in the one or more memories (104, 204) so as to bedriven by the one or more processors (102, 202). The descriptions,functions, procedures, proposals, methods, and/or operational flowchartsdisclosed in this document may be implemented using firmware or softwarein the form of code, instructions, and/or a set of instructions.

The one or more memories (104, 204) may be connected to the one or moreprocessors (102, 202) and store various types of data, signals,messages, information, programs, code, instructions, and/or commands Theone or more memories (104, 204) may be configured by Read-Only Memories(ROMs), Random Access Memories (RAMs), Electrically ErasableProgrammable Read-Only Memories (EPROMs), flash memories, hard drives,registers, cash memories, computer-readable storage media, and/orcombinations thereof. The one or more memories (104, 204) may be locatedat the interior and/or exterior of the one or more processors (102,202). The one or more memories (104, 204) may be connected to the one ormore processors (102, 202) through various technologies such as wired orwireless connection.

The one or more transceivers (106, 206) may transmit user data, controlinformation, and/or radio signals/channels, mentioned in the methodsand/or operational flowcharts of this document, to one or more otherdevices. The one or more transceivers (106, 206) may receive user data,control information, and/or radio signals/channels, mentioned in thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document, from one or moreother devices. For example, the one or more transceivers (106, 206) maybe connected to the one or more processors (102, 202) and transmit andreceive radio signals. For example, the one or more processors (102,202) may perform control so that the one or more transceivers (106, 206)may transmit user data, control information, or radio signals to one ormore other devices. The one or more processors (102, 202) may performcontrol so that the one or more transceivers (106, 206) may receive userdata, control information, or radio signals from one or more otherdevices. The one or more transceivers (106, 206) may be connected to theone or more antennas (108, 208) and the one or more transceivers (106,206) may be configured to transmit and receive user data, controlinformation, and/or radio signals/channels, mentioned in thedescriptions, functions, procedures, proposals, methods, and/oroperational flowcharts disclosed in this document, through the one ormore antennas (108, 208). In this document, the one or more antennas maybe a plurality of physical antennas or a plurality of logical antennas(e.g., antenna ports). The one or more transceivers (106, 206) mayconvert received radio signals/channels, and so on, from RF band signalsinto baseband signals in order to process received user data, controlinformation, radio signals/channels, and so on, using the one or moreprocessors (102, 202). The one or more transceivers (106, 206) mayconvert the user data, control information, radio signals/channels, andso on, processed using the one or more processors (102, 202) from thebase band signals into the RF band signals. For this, the one or moretransceivers (106, 206) may include (analog) oscillators and/or filters.

FIG. 23 shows another example of a wireless device applicable to thepresent specification.

According to FIG. 23 , the wireless device may include at least oneprocessor (102, 202), at least one memory (104, 204), at least onetransceiver (106, 206), and/or one or more antennas (108, 208).

As a difference between the example of the wireless device describedabove in FIG. 22 and the example of the wireless device in FIG. 23 , inFIG. 22 , the processors 102 and 202 and the memories 104 and 204 areseparated, but in the example of FIG. 23 , the memories 104 and 204 areincluded in the processors 102 and 202.

Here, a detailed description of the processors 102 and 202, the memories104 and 204, the transceivers 106 and 206, and the one or more antennas108 and 208 is as described above, in order to avoid unnecessaryrepetition of description, description of repeated description will beomitted.

Hereinafter, an example of a signal processing circuit to which thepresent specification is applied will be described in detail.

FIG. 24 shows a signal process circuit for a transmission signalaccording to an embodiment of the present specification.

Referring to FIG. 24 , a signal processing circuit (1000) may includescramblers (1010), modulators (1020), a layer mapper (1030), a precoder(1040), resource mappers (1050), and signal generators (1060). Anoperation/function of FIG. 24 may be performed, without being limitedto, the processors (102, 202) and/or the transceivers (106, 206) of FIG.22 . Hardware elements of FIG. 24 may be implemented by the processors(102, 202) and/or the transceivers (106, 206) of FIG. 22 . For example,blocks 1010-1060 may be implemented by the processors (102, 202) of FIG.22 . Alternatively, the blocks 1010-1050 may be implemented by theprocessors (102, 202) of FIG. 22 and the block 1060 may be implementedby the transceivers (106, 206) of FIG. 22 .

Codewords may be converted into radio signals via the signal processingcircuit (1000) of FIG. 24 . Herein, the codewords are encoded bitsequences of information blocks. The information blocks may includetransport blocks (e.g., a UL-SCH transport block, a DL-SCH transportblock). The radio signals may be transmitted through various physicalchannels (e.g., a PUSCH and a PDSCH).

More specifically, the codewords may be converted into scrambled bitsequences by the scramblers (1010). Scramble sequences used forscrambling may be generated based on an initialization value, and theinitialization value may include ID information of a wireless device.The scrambled bit sequences may be modulated to modulation symbolsequences by the modulators (1020). A modulation scheme may includepi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying(m-PSK), and m-Quadrature Amplitude Modulation (m-QAM). Complexmodulation symbol sequences may be mapped to one or more transportlayers by the layer mapper (1030). Modulation symbols of each transportlayer may be mapped (precoded) to corresponding antenna port(s) by theprecoder (1040). Outputs z of the precoder (1040) may be obtained bymultiplying outputs y of the layer mapper (1030) by an N*M precodingmatrix W. Herein, N is the number of antenna ports, and M is the numberof transport layers. The precoder (1040) may perform precoding afterperforming transform precoding (e.g., DFT) for complex modulationsymbols. Additionally, the precoder (1040) may perform precoding withoutperforming transform precoding.

The resource mappers (1050) may map modulation symbols of each antennaport to time-frequency resources. The time-frequency resources mayinclude a plurality of symbols (e.g., a CP-OFDMA symbols and DFT-s-OFDMAsymbols) in the time domain and a plurality of subcarriers in thefrequency domain. The signal generators (1060) may generate radiosignals from the mapped modulation symbols and the generated radiosignals may be transmitted to other devices through each antenna. Forthis purpose, the signal generators (1060) may include Inverse FastFourier Transform (IFFT) modules, Cyclic Prefix (CP) inserters,Digital-to-Analog Converters (DACs), frequency uplink converters, and soon.

Signal processing procedures for a signal received in the wirelessdevice may be configured in a reverse manner of the signal processingprocedures (1010-1060) of FIG. 24 . For example, the wireless devices(e.g., 100, 200 of FIG. 22 ) may receive radio signals from the exteriorthrough the antenna ports/transceivers. The received radio signals maybe converted into baseband signals through signal restorers. For this,the signal restorers may include frequency downlink converters,Analog-to-Digital Converters (ADCs), CP remover, and Fast FourierTransform (FFT) modules. Subsequently, the baseband signals may berestored to codewords through a resource demapping procedure, apostcoding procedure, a demodulation processor, and a descramblingprocedure. The codewords may be restored to original information blocksthrough decoding. Therefore, a signal processing circuit (not shown) fora reception signal may include signal restorers, resource demappers, apostcoder, demodulators, descramblers, and decoders.

Hereinafter, a usage example of the wireless to which the presentspecification is applied will be described in detail.

FIG. 25 shows another example of a wireless device according to anembodiment of the present specification. The wireless device may beimplemented in various forms according to a use-case/service (refer toFIG. 21 ).

Referring to FIG. 25 , wireless devices (100, 200) may correspond to thewireless devices (100, 200) of FIG. 22 and may be configured by variouselements, components, units/portions, and/or modules. For example, eachof the wireless devices (100, 200) may include a communication unit(110), a control unit (120), a memory unit (130), and additionalcomponents (140). The communication unit may include a communicationcircuit (112) and transceiver(s) (114). For example, the communicationcircuit (112) may include the one or more processors (102, 202) and/orthe one or more memories (104, 204) of FIG. 22 . For example, thetransceiver(s) (114) may include the one or more transceivers (106, 206)and/or the one or more antennas (108, 208) of FIG. 22 . The control unit(120) is electrically connected to the communication unit (110), thememory (130), and the additional components (140) and controls overalloperation of the wireless devices. For example, the control unit (120)may control an electric/mechanical operation of the wireless devicebased on programs/code/instructions/information stored in the memoryunit (130). The control unit (120) may transmit the information storedin the memory unit (130) to the exterior (e.g., other communicationdevices) via the communication unit (110) through a wireless/wiredinterface or store, in the memory unit (130), information receivedthrough the wireless/wired interface from the exterior (e.g., othercommunication devices) via the communication unit (110).

The additional components (140) may be variously configured according totypes of wireless devices. For example, the additional components (140)may include at least one of a power unit/battery, input/output (I/O)unit, a driving unit, and a computing unit. The wireless device may beimplemented in the form of, without being limited to, the robot (100 aof FIG. 21 ), the vehicles (100 b-1, 100 b-2 of FIG. 21 ), the XR device(100 c of FIG. 21 ), the hand-held device (100 d of FIG. 21 ), the homeappliance (100 e of FIG. 21 ), the IoT device (100 f of FIG. 21 ), adigital broadcast terminal, a hologram device, a public safety device,an MTC device, a medicine device, a fintech device (or a financedevice), a security device, a climate/environment device, the AIserver/device (400 of FIG. 21 ), the BSs (200 of FIG. 21 ), a networknode, and so on. The wireless device may be used in a mobile or fixedplace according to a usage-example/service.

In FIG. 25 , the entirety of the various elements, components,units/portions, and/or modules in the wireless devices (100, 200) may beconnected to each other through a wired interface or at least a partthereof may be wirelessly connected through the communication unit(110). For example, in each of the wireless devices (100, 200), thecontrol unit (120) and the communication unit (110) may be connected bywire and the control unit (120) and first units (e.g., 130, 140) may bewirelessly connected through the communication unit (110). Each element,component, unit/portion, and/or module within the wireless devices (100,200) may further include one or more elements. For example, the controlunit (120) may be configured by a set of one or more processors. As anexample, the control unit (120) may be configured by a set of acommunication control processor, an application processor, an ElectronicControl Unit (ECU), a graphical processing unit, and a memory controlprocessor. As another example, the memory (130) may be configured by aRandom Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory(ROM)), a flash memory, a volatile memory, a non-volatile memory, and/ora combination thereof.

Hereinafter, an example of implementing FIG. 25 will be described indetail with reference to the drawings.

FIG. 26 shows a hand-held device to which the present specification isapplied. The hand-held device may include a smartphone, a smartpad, awearable device (e.g., a smartwatch or a smartglasses), or a portablecomputer (e.g., a notebook). The hand-held device may be referred to asa mobile station (MS), a user terminal (UT), a Mobile Subscriber Station(MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or aWireless Terminal (WT).

Referring to FIG. 26 , a hand-held device (100) may include an antennaunit (108), a communication unit (110), a control unit (120), a memoryunit (130), a power supply unit (140 a), an interface unit (140 b), andan I/O unit (140 c). The antenna unit (108) may be configured as a partof the communication unit (110). Blocks 110-130/140 a-140 c correspondto the blocks 110-130/140 of FIG. 25 , respectively.

The communication unit (110) may transmit and receive signals (e.g.,data and control signals) to and from other wireless devices or BSs. Thecontrol unit (120) may perform various operations by controllingconstituent elements of the hand-held device (100). The control unit(120) may include an Application Processor (AP). The memory unit (130)may store data/parameters/programs/code/instructions (or commands)needed to drive the hand-held device (100). The memory unit (130) maystore input/output data/information. The power supply unit (140 a) maysupply power to the hand-held device (100) and include a wired/wirelesscharging circuit, a battery, and so on. The interface unit (140 b) maysupport connection of the hand-held device (100) to other externaldevices. The interface unit (140 b) may include various ports (e.g., anaudio I/O port and a video I/O port) for connection with externaldevices. The I/O unit (140 c) may input or output videoinformation/signals, audio information/signals, data, and/or informationinput by a user. The I/O unit (140 c) may include a camera, amicrophone, a user input unit, a display unit (140 d), a speaker, and/ora haptic module.

As an example, in the case of data communication, the I/O unit (140 c)may obtain information/signals (e.g., touch, text, voice, images, orvideo) input by a user and the obtained information/signals may bestored in the memory unit (130). The communication unit (110) mayconvert the information/signals stored in the memory into radio signalsand transmit the converted radio signals to other wireless devicesdirectly or to a BS. The communication unit (110) may receive radiosignals from other wireless devices or the BS and then restore thereceived radio signals into original information/signals. The restoredinformation/signals may be stored in the memory unit (130) and may beoutput as various types (e.g., text, voice, images, video, or haptic)through the I/O unit (140 c).

FIG. 27 shows a vehicle or an autonomous vehicle to which the presentspecification is applied. The vehicle or autonomous vehicle may beimplemented by a mobile robot, a car, a train, a manned/unmanned AerialVehicle (AV), a ship, and so on.

Referring to FIG. 27 , a vehicle or autonomous vehicle (100) may includean antenna unit (108), a communication unit (110), a control unit (120),a driving unit (140 a), a power supply unit (140 b), a sensor unit (140c), and an autonomous driving unit (140 d). The antenna unit (108) maybe configured as a part of the communication unit (110). The blocks110/130/140 a-140 d correspond to the blocks 110/130/140 of FIG. 25 ,respectively.

The communication unit (110) may transmit and receive signals (e.g.,data and control signals) to and from external devices such as othervehicles, BSs (e.g., gNBs and road side units), and servers. The controlunit (120) may perform various operations by controlling elements of thevehicle or the autonomous vehicle (100). The control unit (120) mayinclude an Electronic Control Unit (ECU). The driving unit (140 a) maycause the vehicle or the autonomous vehicle (100) to drive on a road.The driving unit (140 a) may include an engine, a motor, a powertrain, awheel, a brake, a steering device, and so on. The power supply unit (140b) may supply power to the vehicle or the autonomous vehicle (100) andinclude a wired/wireless charging circuit, a battery, and so on. Thesensor unit (140 c) may obtain a vehicle state, ambient environmentinformation, user information, and so on. The sensor unit (140 c) mayinclude an Inertial Measurement Unit (IMU) sensor, a collision sensor, awheel sensor, a speed sensor, a slope sensor, a weight sensor, a headingsensor, a position module, a vehicle forward/backward sensor, a batterysensor, a fuel sensor, a tire sensor, a steering sensor, a temperaturesensor, a humidity sensor, an ultrasonic sensor, an illumination sensor,a pedal position sensor, and so on. The autonomous driving unit (140 d)may implement technology for maintaining a lane on which a vehicle isdriving, technology for automatically adjusting speed, such as adaptivecruise control, technology for autonomously driving along a determinedpath, technology for driving by automatically setting a path if adestination is set, and so on.

For example, the communication unit (110) may receive map data, trafficinformation data, and so on, from an external server. The autonomousdriving unit (140 d) may generate an autonomous driving path and adriving plan from the obtained data. The control unit (120) may controlthe driving unit (140 a) such that the vehicle or the autonomous vehicle(100) may move along the autonomous driving path according to thedriving plan (e.g., speed/direction control). In the middle ofautonomous driving, the communication unit (110) mayaperiodically/periodically obtain recent traffic information data fromthe external server and obtain surrounding traffic information data fromneighboring vehicles. In the middle of autonomous driving, the sensorunit (140 c) may obtain a vehicle state and/or surrounding environmentinformation. The autonomous driving unit (140 d) may update theautonomous driving path and the driving plan based on the newly obtaineddata/information. The communication unit (110) may transfer informationon a vehicle position, the autonomous driving path, and/or the drivingplan to the external server. The external server may predict trafficinformation data using AI technology, and so on, based on theinformation collected from vehicles or autonomous vehicles and providethe predicted traffic information data to the vehicles or the autonomousvehicles.

Claims in the present specification may be combined in various ways. Forinstance, technical features in method claims of the presentspecification may be combined to be implemented or performed in anapparatus (or device), and technical features in apparatus claims may becombined to be implemented or performed in a method. Further, technicalfeatures in method claim(s) and apparatus claim(s) may be combined to beimplemented or performed in an apparatus. Further, technical features inmethod claim(s) and apparatus claim(s) may be combined to be implementedor performed in a method.

What is claimed is:
 1. A method for receiving downlink controlinformation in a wireless communication system, the method performed bya user equipment (UE) and comprising: receiving, from a base station,the downlink control information; and receiving, from the base station,a physical downlink shared channel (PDSCH) based on the downlink controlinformation, wherein the downlink control information includes minimumapplicable scheduling offset information, and wherein the minimumapplicable scheduling offset information informs the UE of a minimumapplicable slot offset, wherein the minimum applicable slot offset is anoffset related to the UE not being expected to receive the PDSCH basedon a slot offset smaller than the minimum applicable slot offset, andwherein the minimum applicable slot offset is not applied based on adefault PDSCH time domain resource allocation being used and a PDSCHtransmission being scheduled with a cell-radio network temporaryidentity (C-RNTI), a configured scheduling-RNTI (CS-RNTI) or amodulation and coding scheme-cell-RNTI (MCS-C-RNTI) in a common searchspace associated with a control resource set (CORESET)
 0. 2. The methodof claim 1, wherein the UE receives the PDSCH based on the default PDSCHtime domain resource allocation.
 3. The method of claim 2, wherein theUE receives the PDSCH based on a slot offset defined in the defaultPDSCH time domain resource allocation.
 4. The method of claim 3, whereinthe UE receives the PDSCH in a slot after in which the downlink controlinformation is received plus the slot offset.
 5. The method of claim 1,wherein, based on the default PDSCH time domain resource allocationbeing used and a PDSCH transmission being scheduled with the C-RNTI, theC-RNTI or the MCS-C-RNTI in a UE specific search space (USS) and thecommon search space associated with a CORESET except for the CORESET 0,the UE does not apply the minimum applicable slot offset.
 6. The methodof claim 1, wherein the UE receives minimum applicable slot offsetcandidate information from the base station based on higher layersignaling.
 7. The method of claim 1, wherein the downlink controlinformation is downlink control information (DCI) format 1_1, andwherein DCI format 1_1 schedules the PDSCH.
 8. A user equipment (UE)comprising: a transceiver; at least one memory; and at least oneprocessor operatively connected to the at least one memory and thetransceiver, wherein the processor is configured to: control thetransceiver to receive, from a base station, downlink controlinformation; and control the transceiver to receive, from the basestation, a physical downlink shared channel (PDSCH) based on thedownlink control information, wherein the downlink control informationincludes minimum applicable scheduling offset information, and whereinthe minimum applicable scheduling offset information informs the UE of aminimum applicable slot offset, wherein the minimum applicable slotoffset is an offset related to the UE not being expected to receive thePDSCH based on a slot offset smaller than the minimum applicable slotoffset, and wherein the minimum applicable slot offset is not appliedbased on a default PDSCH time domain resource allocation being used anda PDSCH transmission being scheduled with a cell-radio network temporaryidentity (C-RNTI), a configured scheduling-RNTI (CS-RNTI) or amodulation and coding scheme-cell-RNTI (MCS-C-RNTI) in a common searchspace associated with a control resource set (CORESET)
 0. 9. The UE ofclaim 8, wherein the UE receives the PDSCH based on the default PDSCHtime domain resource allocation.
 10. The UE of claim 9, wherein the UEreceives the PDSCH based on a slot offset defined in the default PDSCHtime domain resource allocation.
 11. A processor configured to: controla transceiver to receive, from a base station, downlink controlinformation; and control the transceiver to receive, from the basestation, a physical downlink shared channel (PDSCH) based on thedownlink control information, wherein the downlink control informationincludes minimum applicable scheduling offset information, and whereinthe minimum applicable scheduling offset information informs the UE of aminimum applicable slot offset, wherein the minimum applicable slotoffset is an offset related to the UE not being expected to receive thePDSCH based on a slot offset smaller than the minimum applicable slotoffset, and wherein the minimum applicable slot offset is not appliedbased on a default PDSCH time domain resource allocation being used anda PDSCH transmission being scheduled with a cell-radio network temporaryidentity (C-RNTI), a configured scheduling-RNTI (CS-RNTI) or amodulation and coding scheme-cell-RNTI (MCS-C-RNTI) in a common searchspace associated with a control resource set (CORESET) 0.